handoff

# Project Handoff Use one client-neutral handshake for every route. Before acting, read `../shared/cross-client-handoff.md` completely and follow its schema and state machine. ## Choose the route - If the user names Claude or Codex, use that client as `to`. - If the user asks for the next or a fresh session without naming a client, set `to` to the current client. This is the default for Claude-to-Claude and Codex-to-Codex continuation. - Use `to: either` only when the task is deliberately client-agnostic. - Set `from` to the current client, or `human` when invoked outside a client session. All routes write `<project-root>/.context/ai-handoff.md`. Do not create a separate client-specific handoff file. ## Prepare a handoff 1. Resolve the project root from the current working directory or the named project. 2. Read only the relevant durable guidance and state: `CLAUDE.md`, `AGENTS.md`, the latest approved plan, current focus, recent log, and any existing handshake. Never inspect restricted `data/raw/` content. 3. Use the supplied outcome. If none is supplied, infer the highest-priority open loop; ask only if different choices would materially change scope. 4. Reconcile the existing handshake. Preserve still-valid decisions and its log, then create a new `handoff_id` and set `status: ready`. 5. Record the source and target client, source and target machine, branch, commit, exact working-tree ownership, observable acceptance criteria, real commands, and the first concrete ac...