handoff

Distill the current session into a handoff document so the next agent can resume cold. ## Accuracy: verify before asserting A handoff is only worth writing if the next agent can trust it and act without re-checking. That makes a wrong fact the worst possible output: a bad path, line number, or "done" claim sends a cold agent down a false trail and costs far more than the handoff ever saved. Silence is safer than a confident error. Almost every wrong fact comes from one habit — writing from memory of the session instead of from the repo as it is *now*. After a long session, or once context has been summarized, recall of specifics gets lossy and the gaps fill with plausible-but-wrong detail. So before a concrete claim goes in, ground it. Treat two kinds of statement differently: - **Checkable facts** — paths, symbol and function names, line numbers, commands, branch, commits, dirty files, and anything you describe as done. Confirm each against the repo as you write it: `git status`, `git log --oneline -10`, and `git diff --stat` for state; Read / Grep / Glob for paths and symbols. Don't transcribe these from memory. If you can't confirm one, it doesn't get asserted — drop it, or mark it `(unverified)` so the next agent knows to check. - **Recollection and judgment** — the plan, why a decision was made, your mental state, what worked and what didn't. These can't be verified against the repo, so write them plainly as recollection and resist inventing specifics to make them s...