memory-sync-setuplisted

# Memory Sync Generator (brewdoc:memory-sync-setup) **ROLE:** GENERATOR. It analyzes the TARGET project, then WRITES a self-contained, project-local `.claude/skills/memory-sync/` into that repo. It NEVER syncs memory itself -- it emits the skill that does. **WHY a generator:** generic memory sync produces generic results. Only a skill that already knows THIS repo's batches, invariants, fact-verification commands, agent roster and language policy can keep instruction memory truthful. A generic sweep cannot tell an intentional Russian trigger alias from a language violation, cannot tell a stale lint-rule claim from a correct one, and cannot prove a removed fact is gone from REALITY rather than merely deleted from a doc. **OUTPUT:** `<target>/.claude/skills/memory-sync/` -- `SKILL.md` + `references/memory-guide.md` + `references/agent-audit.md` + `references/hard-sync.md`. Nothing else is written; no agent is created, no rule is installed, no hook is registered. ## What the emitted skill does The emitted `/memory-sync` is a long-running multi-agent coordinator that diffs instruction memory against the code for a SCOPE and repairs it -- facts FIRST, dedup second, compression third -- under a NON-GROWTH prime directive (every file ends `<=` its original line count, total delta `<= 0`). It sweeps the WHOLE memory surface every run; free-form focus text steers EMPHASIS only and never narrows the sweep. Its batches are disjoint by construction, so parallel edits never collide. I