handbacklisted

Outcome to produce: the user takes one decision and the work under it back, and gets one page a developer can pick up from, with nothing deleted and nothing hidden. Enter the handback flow of the brotherme skill. Run the mechanical command `python3 "${CLAUDE_PLUGIN_ROOT}/tools/bm_lead.py" handback --project-id <id> --decision-id <the decision the user named> --why "<their reason, in their own words>"` (the packaged console script is `bm-lead handback`) and read its output; never describe what happened from memory of this conversation. A plugin install exports `${CLAUDE_PLUGIN_ROOT}` for skill and command content, so that path resolves on its own; on a clone install, where the variable is unset, run `python3 tools/bm_lead.py handback --project-id <id> --decision-id <the decision the user named> --why "<their reason, in their own words>"` instead, from the BrotherMode root (`~/.claude/skills/brothermode`). Either way, run it from the user's project folder so it reads and writes that project's own records. If the user has not named which decision, enter the decisions flow first and let them pick one; never guess. Explain in plain language, before running it, what taking it back does, in this order, because the order is the safety property: 1. Autonomous work stops first. The authorisation the user signed is paused, so nothing else can start while the handover is being written. Pausing is reversible; the authorisation can be resumed later without signing again. 2. What is know