consolidate-memorylisted

# Consolidate Memory ## Purpose Propose a tidied reorganization of one memory store as a reviewable branch/PR. You are the semantic half of a two-part design: all git writes go through `consolidate_pass.py` (the deterministic half), which enforces branch isolation, store scope, and typed commits. This skill is self-contained: follow it identically whether it was invoked as a skill or injected as a system prompt. ## Hard rules - Explicit invocation only: never start a pass on your own initiative. - One store per pass: the store is the directory you were pointed at; it must contain a `MEMORY.md`. If it does not, refuse and report - never guess a different directory. - Never run `git commit`, `git push`, `git checkout`, or `gh pr create` yourself: the wrapper is the only write path. - Never demote content out of its tier or move content to another store: you clean WITHIN the store only. ## The preservation stance (anti-smoothing) LLM consolidation is documented to smooth away rare-but-valid facts. These rules are the countermeasure; they outrank tidiness: - An exception NEVER merges into the rule it excepts. "Always X" + "except in S, do Y" stay distinct facts (merging them into one file is allowed only if both assertions survive verbatim in meaning). - A fact referenced by nothing else is not therefore disposable. - An old date is not staleness. Retire a fact ONLY when a newer fact in this store contradicts it, and cite that newer fact in the commit message. - When