memory-review

# Memory Review Interactive review session for pruning and updating memory entries. ## Data Source Read the entry list from MEMORY-INDEX.md (already in context after session startup). Before displaying the first entry, read the frontmatter of every `active` and `needs-review` file in memory/ to fetch `conf` and `verified` — these fields are not in MEMORY-INDEX.md. Only read the full file body when user picks `update` and needs to modify content. ## Edge Case: Empty MEMORY-INDEX If memory/ is empty or has no active/needs-review entries → display "No memory files to review." and stop. ## Entry Ordering Sort all entries by `verified` date (ascending — oldest first) before starting: 1. `needs-review` entries first 2. `active` entries second 3. `deprecated` — skipped entirely ## Display Per Entry Print this header as plain text output before making the first AskUserQuestion call. Do not repeat it per entry and do not embed it inside any question string: ────────────────────────────────────────────────────────────── 🔬 Memory Review — {N} files to review ──────────��─────────────────────────────────────────────────── Per-entry: use a single AskUserQuestion with entry details embedded in the question text. When constructing the AskUserQuestion tool call, the `question` parameter must contain actual newline characters in the JSON string — not backslash-n (`\n`) escape sequences. **Primary menu** (shown for every entry): - question (use real newlines — the lines below are se...