handofflisted

# Handoff — state that survives the session `/retro` records **permanent lessons**; this records **transient state**. A good capsule lets a stranger (including future-you with zero context) type one command and be productive in two minutes. A stale capsule is worse than none — so capsules are consumed and deleted, never accumulated. ## 1. Write the capsule Create `HANDOFF.md` at the repo root: ```markdown # Handoff — <date> ## Goal <the original request, one paragraph, verbatim enough to re-anchor> ## State - Done: <what is finished, and the verify evidence: command → decisive line> - In progress: <the exact piece mid-flight, and which files hold it> - Verify: <the command(s) to run, fast and full tier> ## Next step <ONE literal command or edit to do first — not a theme, an action> ## Open hypotheses - H1: <suspected cause / approach> — status: <untested | supported by X | refuted by Y> ## Landmines - <thing that looks safe but is not, discovered this session> ``` Rules: - **The next step is literal.** "Continue the refactor" is not a next step; "run `pytest tests/test_auth.py -k refresh` — it is the failing one" is. - **State only what this session knows.** No aspirations, no backlog — that belongs in the issue tracker. - **Refuted hypotheses stay in the capsule** — they are exactly what the next session would otherwise waste an hour re-deriving. If a lesson is permanent (true beyond this task), it also goes through `/retro`. - Uncommitted changes: say so explicit