grounder-handofflisted

Write a session handoff checkpoint to the markdown vault for this project. **Mode lock — write only.** - Never hydrate or start work, regardless of typed extra text (resume / load / hydrate / `/grounder-recall`) — never run `handoff list` to pick or overwrite an existing file. The plain write form of `handoff` (a body argument, no `list`) stays required — that's this command's whole job; always write a **new** file. - Typed extra text is only what the user wrote after `/grounder-handoff` in the chat line — empty or bare command means no extra instruction; ignore any sibling verb that shows up only in a leftover command-payload wrapper. Otherwise, extra text is body guidance for this handoff. - `#N` here means leftover Next item N from *this* session, not file N in a listing. - If the typed text does ask to resume/load/hydrate/`/grounder-recall`, still do this command's job, then add one sentence: saved — run `/grounder-recall` in a new chat to resume. Skip that sentence for "continue in a new session" wording (that's the point of saving) or when the mention only appears in stale payload text. Summarize the session into a structured handoff — not a chat transcript. Do not dump tool traces, full conversation, or false starts. Build a markdown body with these sections (lean; roughly half a screen to one screen): ```markdown # Handoff: <short label> ## Done - … ## Next 1. … # ordered; most important section for resume — required 2. … ## Blockers - None | … ## Decisions