tools-registry-context — load the right design fragment, keep docs honest

tools-registry's design docs are fragments under docs/context/ (one per subsystem), each declaring the source files it covers in frontmatter. MAP.md (next to this file) is the generated reverse index: source file → the fragment that documents it. This skill has two modes.

Mode A — LOAD context (default). Adapt to when you're called:

Cold start (a fresh session, little/no prior context) → warm up. Read docs/context/README.md (the index), then the fragments that matter (the foundation-style overview fragments plus whichever subsystems the query or repo state points at). Run git log --oneline -15 and git status to catch recent commits + uncommitted work. Then give a short orientation — what tools-registry is, the subsystems in play, what changed recently — and say you're ready.

Mid-chat (a task/topic is already in play) → stay targeted. Map the artifacts/topic at hand via MAP.md's "Source file → fragment(s)" table, read just those fragment(s), and proceed. Don't re-warm the whole tree.