Memory audit — the surgical one-file pass

This is the cap-trip response, not the daily ritual. /memory-kit:close-session runs every session and captures; this runs when the hot cache has actually outgrown itself and something must LEAVE it. Keeping them separate is the point: a daily ritual that also has to do surgery becomes a ritual people skip.

Always pause for approval before writing. The user talks; you write — including here.

Inputs

• .claude/memory/MEMORY.md — read in full.
• knowledge/concepts/*.md — filenames + first 5 lines, for duplicate detection (the directory may not exist yet; the first move creates it).
• context/handoffs/ — to confirm a session narrative already lives there → drop, not move.

Step 1 — classify every section

Scan by ## heading. For each, count lines and mark exactly one action: