memory-hygienelisted

# Memory Hygiene **Source framing**: both the Redis architecture guide and the ML Mastery pattern catalog name "forgetting" as the least-solved part of memory systems — "current systems are better at storing and retrieving than deciding what to safely forget" — and both insist explicit retention policy is mandatory precisely because the underlying research problem isn't solved yet. This skill is the operational discipline that substitutes for a not-yet-solved automatic answer: explicit, checkable rules rather than assuming the memory layer manages itself. ## The four jobs bundled here, and why they're one skill Originally conceived as five separate skills (cleanup, health, consistency, diff, merge, validate) — collapsed into one, because in practice they're facets of a single maintenance pass over the same files, not independent workflows a user would invoke separately: **1. Archival (not deletion).** Entries past a reasonable TTL — old checkpoints already folded into an episode by `memory-consolidation`, episodes old enough that nothing has referenced them in a long time — move to `.memory/archive/`, not deleted outright. This preserves the "delete when appropriate" step in the lifecycle as a deliberate, rare, explicit action distinct from routine archival. **2. Conflict detection.** When two memory entries disagree — a semantic fact that contradicts a more recent decision, two episodes describing the same situation differently — flag it explicitly rather than silently