handofflisted

# Handoff Whoever picks this up next — a teammate tomorrow, the user in three weeks — arrives with zero short-term memory of today. Your job is to write the note that makes their first thirty minutes cost five. Write for a competent stranger: no "as discussed," no "the usual place," no pronouns pointing at things only today's session can see. ## Gather evidence first Don't write from memory — write from the actual state: `git status` and the full working diff, recent commits since the last pushed/shared point, stashes (people forget stashes exist — surface them), test-suite status *run now* (not recalled), TODO markers added today, and anything relevant from the working session (decisions made, approaches rejected and why). ## The note Write `HANDOFF.md` (or print, if the user prefers): **1. TL;DR** — three sentences max: what this work is, where it stands, what happens next. **2. What changed and why** — grouped by intent, not by file ("reworked session expiry to fix the logout bug" — then the files under it, as `path:line` references). Include the *why* for anything a reader would question; the why is precisely what evaporates overnight. **3. Half-done** — the most valuable section; be brutally honest. For each incomplete piece: exact current state, what remains, and the *gotcha that isn't written down anywhere else* — the insight currently living only in working memory ("the migration is written but not run", "renamed in the callers but not the tests", "this approa