Session Wrap-Up

A session-end workflow in phases, not a single parallel check. Run them in order:

Preflight — confirm the repo and capture the branch.
Gather (read-only checks 1 to 6) — collect status; write nothing.
Report — deliver one consolidated status checklist.
Commit and push (gated, autonomous) — record side-effects, then commit pending work.
Optional follow-ups (opt-in, batched into one prompt) — skill and learning loops.
Continuation handoff (automatic, gated on open work) — write the prompt that starts the next session.

Report-only mode. If Ane invokes /wrap-up report, /wrap-up --report-only, or asks for status only, run phases 1 to 3 then STOP. Do not write, commit, or run any follow-up, and do not write a handoff.

Date. Use the current date from the session environment. Never guess it.

Phase 1 — Preflight

The thread is now closed. From this point, park every new question, explainer request and follow-up ask in the Phase 6 handoff rather than answering it in-session. Say so in one line when it happens: Parked for the next session: <ask>. Ane can override by repeating the ask, and then you answer it. Reason (2026-07-30 /improve-system Run 4): across five consecutive logged sessions the thread itself closed at 190k–227k and the whole overage came from post-decision Q&A, one extra check, and the wrap-up loops. Closing costs about 50k; answering new asks inside the close-out is what doubles it.