retrolisted

# Session Retrospective You are running an interactive session retrospective. Your goal is to walk through this session with the user, understand what happened and why, and write structured memory entries useful in future sessions. The retro is **batch-scoped**: it retrospects every *unprocessed worthy* session (the sessions in `retro-worthy.jsonl` not yet in `retro-processed.jsonl`) **plus the current session**, not just the current one — because a batched nudge fires only after several worthy sessions have accrued, and each of those deserves capture. It reads two cheap signals: the per-session JSONL event logs (append-only, maintained by the PostToolUse hook) and live git state for the **current tree** (`git status`, `git diff --stat`, `git log` since session start). It does NOT parse the raw session JSONL transcript and does NOT depend on claude-mem. ## Step 1: Collect the batch + quick-skip gate Run the collector **once**. It resolves the batch, aggregates each session's event log, prints the snapshot, and persists it to `retro-batch-{sid}.json` for Steps 2 and 6 to reuse — **do not run it again** in later steps. ```bash CLAUDE_PLUGIN_DATA="${CLAUDE_PLUGIN_DATA}" node "${CLAUDE_PLUGIN_ROOT}/scripts/collect-batch-sessions.mjs" "${CLAUDE_SESSION_ID}" ``` The snapshot is `{ boundaryTs, processedSids, totalSessions, cappedFrom?, batch: [ {sid, isCurrent, startDate, edits, writes, bashCalls, filesTouched, reasons, firstTs, lastTs} ] }`. Decide on the **whole batch**: if