memory-tidylisted

# Memory tidy ## Scope and triggers MEMORY.md index drift covers notes missing from the index and index entries with no file. Also fires when a scheduled run asks for the memory-tidy audit of a repository. The excluded auto-memory under `~/.claude/projects` is machine-local: not git-tracked, no PR gate. ## Overview Audit a repo's git-tracked `.claude/memory/` store and ship the cleanup as a PR. Core principle: **every verdict cites checkable evidence, and deletions reach main only through a PR merge**, the PR is the operator's approval gate, so the audit itself never needs to ask permission. This is the judgment half of the kit's memory plane. The mechanical half is `stats memory-sweep` (lib/stats): a read-only scanner that never writes. This skill consumes its output and is the only path that edits a store, always behind a PR. ## Process 1. **Branch in a worktree first** (native worktree tool). All edits and deletions ride this branch. Touching the store on the current branch is the failure this skill exists to prevent. 2. **Mechanical pre-pass.** Run `uv run stats memory-sweep` from the kit's `lib/stats/` and filter its JSON for this repo's store: dead path refs per note, stale index entries. Always also diff both directions: the note files on disk vs the entries in `MEMORY.md` (files not indexed are invisible to sessions; entries with no file are ghosts). 3. **Fan-out judgment.** Split the notes into 2-4 subsystem clusters (roughly one cluster per 40 notes; a tiny