groom-noteslisted

# Groom Notes Review all notes in `docs/notes.toml` — clean up stale ones and suggest new ones from recent work. ## Phase 1: Prune 1. **Parse notes**: Read `docs/notes.toml` and list all notes with their sentiment, text preview, and mentions. 2. **Identify candidates for removal**: - Notes that reference removed/renamed files (check with `Glob`) - Notes that contradict current code (e.g., "X doesn't work" when X was fixed) - Duplicate or near-duplicate notes covering the same topic - Notes about temporary issues that have been resolved - Notes with stale mentions (files that no longer exist) 3. **Present findings**: Show a summary of candidates grouped by reason: - **Stale**: References removed code or fixed issues - **Superseded**: Newer note covers the same ground - **Duplicate**: Multiple notes saying essentially the same thing - **Update mentions**: File paths that moved but lesson is still valid 4. **Get approval**: Present the list of proposed changes. Ask the user to confirm before making changes. 5. **Execute**: Use `cqs notes remove` / `cqs notes update` CLI commands. If the CLI isn't available, edit `docs/notes.toml` directly. 6. **Report**: Show before/after count and what was changed. ## Phase 2: Suggest After pruning, scan for note-worthy events that aren't already captured: 1. **Check recent git history**: `git log --since="1 week ago" --oneline` (or since last groom) 2. **Look for surprise-worthy patterns**: - Bug fixes