handoff-docslisted

# Handoff docs The bar is the same one `to-issues` sets for tickets: a reader with the repo and no memory of this conversation must be able to continue without asking a question back. ## What a handoff doc is not It is not the ticket system, and it is not the decisions log. A handoff doc is read once, by whoever opens the next session, and then archived — it is never treated as living truth the way a ticket or a decisions-log entry is. Anything actionable belongs in a ticket (with `verify`/`touches`/`executor` per `tickets-protocol`) or a dated decisions-log entry, not only in the handoff doc. A handoff doc that is the *only* record of a decision is a decision that will be lost the moment the doc goes stale, because nobody re-reads an old handoff doc looking for ground truth — they read the current tickets and the current docs. Treat the handoff doc as a pointer and a summary, not a container. ## Structure - **What changed this session** — bullets naming capabilities delivered, not internal jargon or ticket ids alone. Someone skimming this should know what is different now. - **Verified vs. assumed** — state facts as verified only if they actually were (a command run, an output read); mark anything else as an assumption. A confident-sounding guess here is worse than an open question, because the next session acts on it without checking. - **What remains** — as ticket ids/links if tickets exist for the remaining work, not prose that duplicates what the ticket