[yw0nam]

Summary

The domain glossary moves from CONTEXT.md to GLOSSARY.md. The mattpocock-skills engineering skills (domain-modeling, grill-with-docs, tdd, code-review, diagnosing-bugs) read and write GLOSSARY.md by that fixed name, so with CONTEXT.md they would start a second glossary.

CONTEXT.md              -> GLOSSARY.md        (git mv, content unchanged)
AGENTS.md               Domain docs line names GLOSSARY.md
docs/agents/domain.md   replaced by the plugin's current domain.md (GLOSSARY.md / GLOSSARY-MAP.md)
docs/adr/0011, 0013     status line cites GLOSSARY.md

Owner decision: rename the file instead of telling each skill that the glossary is CONTEXT.md.

Related issues

None.

Runtime evidence (required for ingest / retrieval / serving behavior)

N/A — no runtime behavior change (docs only). grep -rn CONTEXT --include=*.md over the tree returns nothing.

Verification

• uv run pytest passes (integration tests run locally against a throwaway Postgres container and the live embedder) — N/A, no code change
• uv run ruff format --check . and uv run ruff check . pass — N/A, no code change
• docker compose build mcp passes (Dockerfile / dependency changes) — N/A
• Runtime evidence attached above, or N/A justified

Checklist (core principles)

• Selective storage — notes stay distilled; verbatim text lives only in doc_rows and the turns lane
• Source-specific logic stays out of the source-agnostic core (ingest pipeline, retrieval, serving)
• No hardcoded endpoints/models — configuration lives in .env
• New/changed behavior ships a test in this PR (or skip-tests label justified) — no behavior change