session-handofflisted

# Session handoff The next session starts with zero memory of this one. The handoff is the only thing that lets it pick up without re-deriving everything from scratch. Make it genuinely comprehensive - not a terse note, but the full story of the session, grounded in real git data rather than recall. Write to `HANDOFF.md` at the repo root. This is live session state, so it is always gitignored - see "The file is always ignored" below. ## Pull real data first, never recall Before writing a word, gather ground truth. Recall drifts - the git log does not. - `git log` since the last handoff: commit hashes and subjects. Do not paraphrase these from memory. - `git status`: uncommitted or dirty files. - Current branch, and whether HEAD is pushed or ahead of origin. - Read the existing `HANDOFF.md` if there is one, so you continue its timeline instead of starting over. If it is the first-ever handoff (no file yet), or the repo has no commits, or HEAD is detached - say so plainly and work from whatever ground truth exists. Do not invent a history that is not there. ## Match the project's voice, do not impose one Read a few recent commit messages and any existing docs, and write the handoff in that voice. A handoff that sounds like the rest of the project reads as part of it; one in a generic assistant register reads as bolted on. The project sets the tone, not the skill. ## Structure - use these sections, in this order ### Session date and headline The date, and a one-line headl