wrapuplisted

# Session Summary (TL;DR) Generates a summary of this session and saves it to the logs folder for future recall. --- ## Scope /wrapup writes the session log only. It does NOT promote insights to memory/ — that is /recap's responsibility. Do not write to MEMORY.md or memory/ files. --- ## Session Log Frontmatter See `skills/startup/references/session-formats.md` → Session Log Format for frontmatter variants and body sections. **Never add `recapped:` or `topics:`** — those are populated by /recap later. --- ## Step 0: Active Pause Thread Detection Run this BEFORE Step 1. 1. Read `[logs_folder]/pause/_active.md`. If absent or empty → set `wrapup_mode = "session"`; skip to Step 1 (zero-overhead path for non-pause sessions). 2. If a slug is present: parse the file's single-line content as `slug`. Glob `[logs_folder]/pause/*-{slug}-pause-*.md` → `pause_count` (file count) and derive `first_date` = earliest `YYYY-MM-DD` date prefix among matched files (used in Step 3's question text). 3. Use `AskUserQuestion`: Question: "Active pause thread: `{slug}` ({pause_count} snapshots since {first_date}). Wrap up this thread now?" Options: - "Yes — consolidate into one session log" (sets `wrapup_mode = "thread"`) - "No — wrapup today's work only; keep pause thread active" (sets `wrapup_mode = "session"`) 4. If `wrapup_mode = "session"` AND active pause exists → fall through to **Step 0b: Auto-Finalize Pause** (below) BEFORE proceeding to Step 1. 5. If `wrapup_mode = "