memory-cleanup

# Memory Cleanup — Manual Dream Process Implements the 4-phase memory consolidation process modelled after Claude Code's Auto Dream feature. Run after major refactors, framework migrations, or every 5+ sessions in a repo. The memory system lives at `~/.claude/projects/<encoded-cwd>/memory/` and consists of: - `MEMORY.md` — index file (must stay under 200 lines; lines after 200 are truncated by the harness). - Topic files — one Markdown file per memory entry with YAML frontmatter (`name`, `description`, `metadata.type`). The four memory types are `user`, `feedback`, `project`, `reference` (see global `auto memory` instructions for semantics). This skill never invents new types. ## Argument Handling (Phase 0) This skill accepts two optional flags. Default (no flag) runs the interactive 4-phase consolidation defined below. | Flag | Behavior | |---|---| | `--dry-run` | Run Phases 1-3 read-only; instead of mutating MEMORY.md / topic files, write a unified-diff proposal to `.orchestrator/pending-dream.md` (atomic). Exit 0. | | `--apply-pending` | Read `.orchestrator/pending-dream.md`; refuse if older than 14 days; apply diff; delete pending file; print `auto-dream applied: -<X> lines, +<Y> entries`. Exit 0. | Flags are mutually exclusive — passing both is an error. Absence of both = legacy interactive mode (Phases 1-4 below). **`--dry-run` flow:** - Read MEMORY.md and topic files (read-only). - Produce the same internal plan the interactive mode would (merges, prunes, rewr...