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.
1The msg tool is live fleet-wide from an uncommitted working-tree edit. ~/.local/bin/msg symlinks into a shared checkout parked on an unrelated branch (fix/ra-verify-submit) where the file is modified but uncommitted; a git stash or branch switch there silently reverts msg for every session, and --body-file callers would have the flag treated as literal message text. Identical bytes are committed and pushed as PR agent-smith#207 (CI green, unmerged). How should this be closed?
In plain terms. The tool every session here uses to message every other session is running from an edit that was never saved. It works right now, and it's the fix you asked for. But it's sitting in a scratch area, and an ordinary bit of tidying by anyone working nearby would wipe it out for everyone at once, with no error and no warning — messages would just start losing words again. The saved copy is ready and passed all its checks; it only needs your approval to become the one in use.
Fable recommends: Merge PR 207 — the durable fix; the risk window closes properly It is the only option with no cleanup obligation. The stopgap works and fails loudly rather than silently if the worktree is later removed, but it creates a temporary pin that must be REMEMBERED and undone after the merge — and a fact that has to be remembered to stay true is exactly the failure class this task is about. Tried first, unsuccessfully: receipt f0bbf6a66 — RESOLVED (exit 0), not a needs-human. It chose the repoint, having found the clean worktree I had missed, and I verified its facts independently (branch fix/msg-body-file, HEAD 7d55f58, clean tree, sha 60a181c070b3 identical to live). It reaches you anyway because EXECUTING it was denied by a permission gate: an adviser's exit 0 lets me stop asking, but it cannot authorise mutating the binary every session on this machine runs. Supersedes withdrawn b86370412, which asked the same thing in engineering language.