clean-memorylisted

# Clean up memory Memory lives on two surfaces, cleaned differently. First work out which one is meant. | Surface | What is there | Cleaned by | |---|---|---| | **File memory** `${user_config.memory_dir}` | facts about the user, decisions, pitfalls; `mistakes/` | editing files, under git | | **MemPalace** | the index of the vault `${user_config.vault_dir}`: what lives where | `mempalace_delete_drawer` | The user said "clean the memory" without saying which: **ask in one line**. ## File memory It is under git, so cleaning is safe: everything is recoverable through `git log -p`. 1. Read `MEMORY.md` and the folder. 2. Look for four things: - **contradictions**: two entries say different things about the same subject; - **outdated**: the date passed, the work is done, the fact no longer holds; - **description drifted from content**: the entry will stop being recalled; - **episodes instead of facts**: "did X on such a day" is derivable from git and the vault. 3. **Retire what is outdated, do not overwrite it**: mark from which date it no longer holds and what replaced it. 4. Deleting a whole file: **only with the user's confirmation**. 5. Keep the index under 150 lines and 20 KB: one line per entry. Measure: `python "${CLAUDE_PLUGIN_ROOT}/scripts/memory_eval.py" --memory "${user_config.memory_dir}" --dry` ## MemPalace 1. `mempalace_status`: how many drawers, how they are spread across wings. 2. **Narrow the scope before listing.** There can be thousands o