long-running: 🐛 the root ends a done Orca lane with orca-gc --done

[yasyf]

Context: At 2:06 AM on October 6, 2026, the owner ruled that the root ends a done Orca lane itself (cc-notes answer edfa70e): "if a lane is done you can just terminate it no need to do this dumb signal thing". Before that ruling, O6 and R195 let the root reclaim a lane only after the lane sent worker_done. So a stood-down or superseded lane had to be messaged and asked to report completion before anything could end it.

Summary: O6 and R195 give the root a second route. Once it decides a lane in its own Run is done (stood down, superseded, or its deliverable on disk), it runs orca-gc --run <run> --done <ctx>. That call stops the worker, closes its terminal, and reclaims its worktree under the existing rules. The remote-worker paragraph keeps remote runtimes and workspaces, and points local lanes at the same route.

Motivation: The root already owns the Run and the decision. Messaging the lane to send worker_done adds a round trip and protects nothing. The other session protections are unchanged: no pkill, no signals, no bulk closes, and the runner still never ends a session.

Details: The --done verb ships in Forge-AI/monorepo's .agents/skills/orca/scripts/orca-gc. The captain-hook sessions guard change that allows a bare worker-stop from the coordinating root is yasyf/captain-hook#320. long-running goes from 0.6.153 to 0.6.154.