grounder-recalllisted

Recall this session from the latest vault handoff and repo truth. **Mode lock — load only.** - Never write to the vault, regardless of typed extra text (save / handoff / checkpoint / continue in a new session) — never run the write form of `handoff` (the one that takes a body argument). The read-only `handoff list` lookups in the steps below stay required — they are not the ban. - Typed extra text is only what the user wrote after `/grounder-recall` 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. - `#N` is a session pick only when the typed text *is* a selector (`#1`, `resume auth-middleware`). If `#N` sits inside save/explain prose instead, load the latest — do not guess an index. - If the typed text does ask to save/handoff/checkpoint/continue in a new session, still do this command's job, then add one sentence: did not save — run `/grounder-handoff`. Skip that sentence when the mention only appears in stale payload text. Read-only — do not write to the vault. Do not invent vault paths. **Special case: the instruction asks to view existing handoffs, not recall** (`list`, `list 3 oldest`, `show handoffs`, etc.) → run `{{GROUNDER_CLI}} handoff list --limit <N> --markdown` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no recall, no `AGENTS.md`, no “start work.” Relay the CLI stdout as-is (