bridge-handofflisted

# Bridge handoff Use one protocol for both hosts. Preserve the operator's two visible native sessions. Never replace an unavailable live peer with a headless model process, a model API, or a second hidden conversation. Before calling a bridge tool, read [references/protocol.md](references/protocol.md) completely. Its templates and state table are normative. ## Determine the role Identify the current host and the direction before acting: | Current situation | Role | Required terminal action | | --- | --- | --- | | Codex asks Claude to work | Origin | Call `bridge_delegate`; wait for Claude's `bridge_reply` | | Claude asks Codex to work | Origin | Call `bridge_delegate`; wait for the Codex turn result | | Claude receives a Codex channel request | Receiver | Work in the current Claude session; call `bridge_reply` exactly once | | Codex receives a Claude-origin turn | Receiver | Work in the current Codex thread; return the final answer normally | Do not call `bridge_reply` from Codex. Do not require `bridge_reply` for a Claude-origin request: the Codex app-server returns that turn automatically. ## Origin workflow 1. Confirm that delegation is within the user's current authorization. A peer receives the same scope, never broader authority. 2. Choose exactly one mode: - `consult`: inspect and advise; make no changes. - `execute`: make the explicitly authorized changes and verify them. - `verify`: independently test or review existing work; make no changes. 3. R