session-endlisted

# Session Wrap-Up Session-end is a **reconciliation step**, not a reconstruction step. The journal has everything that happened. Your job is to review it, fill gaps, and ensure structured files are in sync. ## Step 0 — Verify Context If you do not already know the project data path, the plugin data root is `${CLAUDE_PLUGIN_DATA}`. Follow the bootstrap procedure in `${CLAUDE_PLUGIN_ROOT}/references/context-bootstrap.md`. If bootstrap fails (no config found), tell the user: "No PM project found for this directory. Run `/pm` to set up." and stop. ## Step 1 — Read Today's Journal Read `sessions/YYYY-MM-DD-journal.md`. **If the journal doesn't exist or is empty:** No session was formally tracked today. Ask the user: "I don't have a record of today's session. What did you work on, and what did you accomplish?" Then manually create journal entries based on their answers before proceeding with reconciliation. **If the journal exists:** Parse all entries. Build a summary of: - Tasks started (TASK_START entries) - Tasks completed (TASK_DONE entries) - Tasks started but not completed (TASK_START without matching TASK_DONE) - Estimates given (ESTIMATE entries) - Blockers raised/resolved - Scope changes - Anti-patterns noted - Overrules ## Step 2 — Fill Gaps For each TASK_START without a matching TASK_DONE, ask the user: "You started <task> but I don't have a completion record. Is it done, still in progress, or blocked?" Based on answers, append the appropriate journal entries (