memory-auditlisted

# Memory Audit Run a memory hygiene pass on the project's `memory/` directory. If `memory/` does not exist in the current project, report that and stop. ## 1. Review active files for staleness 1. Use `Glob("memory/**/*.md")` to discover all memory files. 2. Skip files with `status: superseded` or `status: archived` — these are history only. 3. For each **active** file, check whether it still accurately describes the codebase as it exists today: - Does it reference a service, module, or dependency that no longer exists? - Has the technology it covers been removed or replaced? - Does a more recent decision supersede it? 4. For stale files: - Context no longer applies → update `**Status:** archived` - Superseded by a newer decision → update `**Status:** superseded` and populate `**Superseded-by:**` 5. Do not delete files — history is preserved by archiving, not deletion. ## 2. Check for gaps in decision coverage After reviewing active files, look for unrecorded decisions. Ask the user: > "Are there major architectural decisions, known issues, or pattern choices that have been made but aren't recorded in memory? For example: a technology that was evaluated and rejected, a workaround for a platform constraint, or a deliberate deviation from the conventions." If the user identifies gaps, offer to create new memory entries for them using the templates in `docs/MEMORY-WRITING.md`. ## 3. Report Output a summary: - Total active files reviewed - Files archived (