Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1Merge PR #3 (watcher-doctor: a session whose alarm clock dies is now spotted by an outside sweep)? It installs a background job that runs every 3 minutes and — if a safety file is ever removed — could wake sessions on its own.
Fable recommends: Merge it, and leave the background job in report-only mode (it just names the sleeping sessions; a human still wakes them) It is verified working: I killed this session's own alarm clock and the outside sweep noticed 3m45s later with nobody watching, and it correctly left 18 healthy sessions alone. On its first run it found 10 other sessions across the fleet that had genuinely gone dark and never knew — 7 of them are sessions waiting on YOU to answer something, which is exactly the case where nobody notices. Report-only keeps a human in the loop for the waking part. ⚠️ Time matters slightly: the fix is currently only alive because this machine's command folder is sitting on the unmerged branch. If that gets switched or reset before the merge, the fix disappears and the problem comes straight back. Tried first, unsuccessfully: f217cec58 — RESOLVED, held under reversal (high/high). It read watcher-doctor in full and said this is literally an 'autonomy arm', which my own merge gate excludes, so I must not merge it myself: 'a self-merge gate is worthless if the constrained party reads ambiguity in its own favor.' It also noted the repo has no CI and no code review, and that the code is already running on the box anyway — so waiting costs a round-trip, not protection.