session-retrospective

# Session Retrospective Structured post-implementation analysis. Evaluates the current run across five dimensions, persists findings in MCP, and maintains cross-session trend memory to surface actionable improvement proposals. --- ## Step 0 — Mode Check If `$ARGUMENTS` contains `--dry-run`, set **DRY_RUN = true**. In dry-run mode, perform steps 1-4 and render the report (step 9) but skip steps 5-8 (no MCP item creation, no memory updates). Announce at the top of the report: `**Dry run** — no items created, no memory updated.` --- ## Step 1 — Gather Scope Determine which items to analyze by collecting distributed `session-tracking` notes. ### 1a. Identify items in scope **If `$ARGUMENTS` contains a UUID (root item ID):** ``` query_items(operation="overview", itemId="<root-uuid>") ``` This returns the root item and its children. Collect all item UUIDs from the overview. A supplied root UUID is the **authoritative scope** — this covers dispatched mode, e.g. a background agent invoked with the root item ID (see the output style's hook-driven Retrospective dispatch, or the retro-trigger hook's background-agent directive). When a root UUID is supplied, run only this overview call and do **not** run the fallback scan below (neither the `get_context` calls nor the terminal-items search) — the fallback scan applies only when no UUID argument was provided. **If no root item ID provided:** Check for a known project root: session context injected by the SessionStart hook, o...