handofflisted

# Handoff A handoff is a compact record of ONE task being handed over. It records what the next actor must know to continue and complete the work — no more, no less. It anchors at the **seam**: the joint where this session's work ends and the next's begins. The seam is a concept; in rosary it is *addressed* by an anchor bead, but the two are not identical — a session has exactly one seam even when it touches several beads or none. Reframing from "which bead?" to "where is the seam?" is what lets this skill anchor cleanly regardless of how messy the session was. **MCP dependency:** rosary (`rsry_*`). Uses `rsry_agent_session_message_record`, `rsry_bead_comment`, `rsry_workspace_checkpoint`, `rsry_bead_create`, `rsry_bead_history`, `rsry_dispatch_history`, `rsry_agent_run_events`, `rsry_status`, `rsry_expand_ref`, `rsry_list_beads`, `rsry_active`. If rosary is unavailable, fall back to WRITE step 5.4 only (the `/tmp` markdown) and tell the user the graph anchor was skipped. The invocation argument (`$ARGUMENTS`) answers **"what will the next session be used for?"** — it is the sole source of scope. Every field you write must trace back to it. --- ## 0. Resolve mode If `$ARGUMENTS` begins with `--resume`, this is a pickup: go to **§6 RESUME**. Otherwise this is a WRITE handoff: continue with §1. --- ## 1. Resolve the seam (WRITE) The mailbox entry needs exactly one anchor bead. Resolve it by this precedence. **Detection proposes; the human confirms — never anchor a han