wrap-sessionlisted

# Wrap Session End the current session cleanly so the next one picks up without losing a beat. --- ## Step 1: Update `docs/archived/implementation-docs/9-oss-ready/active.md` Read `docs/archived/implementation-docs/9-oss-ready/active.md`, then update the **Status** section to reflect: - What was just completed this session - What we're doing next session - Current state of the overall work Keep the rest of active.md intact (Current Focus, What We're Doing, Deliverables). Only the Status section changes. --- ## Step 2: Log the Session 1. Check `docs/archived/implementation-docs/9-oss-ready/sessions/` for the latest session number 2. Create the next sequential file (e.g., `002.md`, `003.md`) Format: ```markdown # Session [NNN] — [YYYY-MM-DD] ## What Happened [2-4 sentences summarizing the session. Be succinct.] ## Decisions Made [Numbered list of decisions, or "None" if purely execution work.] ## What's Next [What the next session should start with.] ``` --- ## Step 3: Commit Run `/commit` to stage and commit all changes from this session. --- ## Step 4: Starter Prompt Generate a starter prompt for the next session. This is a self-contained message the user can paste into a fresh chat to pick up exactly where this session ended. The prompt should: - Tell the agent which files to read first (always start with `docs/archived/implementation-docs/9-oss-ready/active.md`, then the latest session log) - Include any phase-specific files relevant to the current wo