zanmaiclose-sessionlisted

# close-session Persistent hand-off at session close. Four sections, no more. ## Directive Four sections, in this order, every time: Done, Next, Intent, Realignments. Adding a fifth section is out of scope for a session close. If a piece of content does not fit one of the four, ask whether it belongs in `zanmai/memory/general.md` instead. ## When to use - The user signals end-of-session in their writing language (close session, wrap up, we are done, end for today). - The user invokes `/zanmai-close-session`. - Steve detects the session is winding down and offers to close. ## When not to use - Mid-session note taking. Use the bundle's own file for that. - Capturing a single fact. Use the bundle or `zanmai/memory/general.md`. - The user wants a status report mid-session. That is a manual ask, not a session close. ## The four sections ### Done What was actually accomplished. Concrete artefacts (files written, decisions taken, imports completed). Not "we discussed". Not "we considered". Things that exist after the session that did not exist before. ### Next The single most important next step for the next session. Plus one backup item if there is a natural follow-up. One or two items, not a backlog. The full backlog lives elsewhere, this is the entry point for the next session. **Before this section is written, every open point of the session goes onto a work object.** For each one that is still open: `zanmai.py work open` where no object exists yet, then `zanmai.py