end-sessionlisted

The two continuity mechanisms this project has — `.claude/handover.md` and the auto-memory system — solve different problems and neither replaces the other: - **Handover** is ephemeral, task-in-flight state: what's staged but unverified, the exact next step, uncommitted git state. It exists only to give a resumed session the same continuity as `claude -c` without replaying the whole prior transcript (and its token cost) on every turn after. It's overwritten each time, gitignored, and only useful right before something reboots the session. - **Memory** is durable, cross-session narrative — decisions, feedback, ongoing project facts. It's meant to accumulate over months, not describe what to do the moment the session resumes. The auto-memory system's own rules already exclude ephemeral task state from it, so this is not duplicate coverage — dumping handover-shaped content into memory would violate its scope, same as leaving durable narrative in a file that gets overwritten next time. `end-session` exists so the user doesn't have to decide which applies — run this at the end of every session, reboot-pending or not. ## Steps 1. **Decide if a reboot is actually pending.** - Run `rpm-ostree status` — a staged deployment not yet booted is the primary signal on this Silverblue machine. - Also weigh anything this session proposed but hasn't yet executed that needs a restart to take effect (kernel module changes, certain `systemctl` unit c