handoverlisted

Normally reached via `/end-session`, which checks whether a reboot is actually pending and invokes this skill's write mode only if so — don't make the user track which mechanism applies. Invoke this skill directly when you already know a reboot is imminent and want the snapshot written without going through that check. Formalizes the standing practice already recorded in this project's memory (`feedback-handover-over-dash-c`): `claude -c` replays the entire prior transcript as input tokens on every subsequent turn, including large one-time outputs like full `rpm-ostree install` dumps — on a long bootstrap-style session that cost compounds every turn for the rest of the session. A bounded handover file plus memory gives the same continuity for a fixed, small cost instead. ## Write mode — before a session-ending action Trigger proactively, without being asked, before `systemctl reboot`, `rpm-ostree rebase`, or anything else that requires a restart. 1. Snapshot: what's confirmed done, what's staged-but-unverified, known blockers, and the exact next step. 2. Explicitly check and record uncommitted/pending git state — `git status` / `git diff --cached` across any repo touched this session. This is a recurring near-miss; don't skip it. 3. Overwrite `.claude/handover.md` wholesale (gitignored, repo root) — never append. It's working state, not a log; once consumed and the phase it described has moved on, the next write replaces it rather than piling up. Durable