memory-bank-defraglisted

# Memory Bank Defrag Bring a project's memory bank back in sync with reality and remove cruft. The memory bank is three things: 1. **`.assistant/`** in the repo — the durable, version-controlled knowledge base (project context, requirements, decisions/ADRs, scope, open questions, stakeholders, glossary). Structure varies per project; operate on whatever files exist, don't assume a fixed layout. 2. **Auto-memory** — the cross-session memory at `~/.claude/projects/<slugified-cwd>/memory/` (an `MEMORY.md` index plus one file per fact). Local only — **absent on cloud/headless runs**; skip silently if the directory doesn't exist. 3. **Repo current-state docs** — files that assert *what is true now* and drift the same way: `README.md`, `AGENTS.md`/`CLAUDE.md`, design specs, proposals. Update these when a recent commit makes them stale. Do **not** touch raw source records that capture *what happened* — meeting transcripts, chat dumps, extracted board content — those are evidence; keep them verbatim (translate only by adding a summary alongside, never by overwriting). The job is **defragmentation**, not rewriting: same facts, fewer patches. Amendment-on-amendment trails collapse into one current-state statement; resolved questions get closed; stale facts get corrected against the actual code/docs; new durable facts from recent commits get captured. ## Non-negotiables - **Accuracy > speed.** Memory is point-in-time and may be wrong. Before you a