call-it-a-daylisted

# Capture the session handoff Discover actual project conventions through applicable AGENTS.md instructions and existing documents. Do not invent private memory locations or assume a host memory service exists. The next session should be able to read at most three existing entry-point documents and know what shipped, where unfinished work stopped, the first action to take, and decisions affecting that work. Multi-plan entry points can link to each plan's detailed status record. ## 1. Classify and reconcile State whether this was an active-plan, multi-plan, ad-hoc, or empty day. Check Git status/history, the in-session record, and verification results. Separate committed work, uncommitted changes, decisions, proposals, and pending checks. Flag unexpected changes without claiming them as this session's work. Reuse relevant test/lint/typecheck results obtained against the final state. Run missing or stale checks appropriate to the changes. Record actual commands/results; label unavailable checks instead of inventing counts. Use absolute dates in durable records. ## 2. Rewrite the existing resume prompt Locate the existing resume file, for example docs/prompt.md, RESUME.md, or NEXT.md. If no convention exists, ask where the handoff belongs before creating one; prepare its content while waiting. Rewrite it with: - State summary: active plan/chunk, completed outcome, and next work. - Ordered documents to read first, including precise plan sections where useful. - Shipped