handoff-orchestratorlisted

# Hand off one orchestrator scope ## 1. Get approval A handoff creates another user-facing window, so the current main agent first presents one approval decision, naming the scope that moves and any work this orchestrator retains. A new tab is created only after the user approves. ## 2. Carry continuity Pass only goal and scope, confirmed decisions and user terms, current state and evidence, next action, and exclusions. Omit empty fields and conversation text. ## 3. Launch and transfer Run `handoff-orchestrator.py` with `--user-approved`, this pane, cwd, provider, and the continuity fields. Pass `--dispatch` for each in-progress dispatch in the moving scope; a handoff that retains nothing lists every dispatch this pane coordinates. The script creates and labels an independent tab, starts the receiving orchestrator, prompts it to invoke `boss-say` and then accept, and verifies the handshake after that route is established. It waits up to two 120-second acceptance windows, re-offering only to a receiver that stopped without accepting, so give the command a tool timeout of at least five minutes. Final failure closes the new tab and leaves ownership here. ## 4. Leave the scope On acceptance, status events, investigation, scheduling, reporting, and cleanup all belong to the receiver. Report the new tab and transferred scope compactly. Continue only the scope passed through `--retains`. When none is retained, let the launcher close this pane after it emits the accepted resu