memory-consolidatelisted

# Memory Consolidate This is a periodic pass, not a per-session check. Run it so a future session can orient on who the user works with, what they are focused on now, and how they like to work, by reading a small, current set of memories instead of re-deriving that context or re-asking the user. This is separate from `memory-maintenance`, which measures store health, and `curating-memories`, which curates the Forgetful store. It owns the reflective Serena file pass because neither sibling merges duplicate topic memories or separates durable user context from dated work. ## Triggers Use this skill when the user says: - `consolidate memory` for a full durable-versus-dated review and index tidy - `consolidate Serena memory` for pruning stale or thin Serena memory files - `merge memory files` for combining overlapping topic files - `tidy the memory index` for trimming `memory-index.md` alone ## Tool Order Use these steps in order: 1. **Inventory with Serena.** Use Serena's list-memories capability only after confirming Serena is active on the repository being consolidated. If the active project is unknown, different, unavailable, or the Serena call errors or times out, stop after Phase 1 without reading or writing memory files. 2. **Validate size from Serena content.** After Phase 1's gates pass, apply the atomicity limits documented by `memory-maintenance` to the content Serena already returned. Do not invoke a second filesystem reader. Before any writ