internal-shipped-referencelisted

# Internal shipped reference `src/shipped/references.ts` classifies five same-repository reference forms by pattern and stops there on purpose. Its own `DOCS_PATH` comment names the sixth: telling a `canon/context/<name>.md` citation of this repository's own domain entry apart from an illustration of a target's own generic tree, such as `canon/context/index.md`, is a semantic read no pattern makes. This skill is that read, plus the parallel judgment over a layout or count claim. ## Discriminator Read every added or changed line in the diff under this rule's eight corpora: `internal/`, `standards/`, `snippets/`, `claude/`, `governance/`, `docs/`, `scripts/`, `tooling/`. For each `canon/context/<name>.md` token: - **Fine.** The sentence reads as an instruction for a target session to consult its own project's copy if one exists, or illustrates the path shape a target's own tree would take, never naming a fact only this checkout holds. `ux-measure/SKILL.md`'s `canon/context/development/: the documented run commands and the port each serves` is this case, read as "check your own project's entry." - **Fails.** The sentence names a fact true of this repository specifically, one only this checkout's own `canon/context/` resolves, such as a documented decision or a domain narrative a target reader cannot open. `canon-cli/SKILL.md`'s prior citation of the tooling context entry as "the toolkit's" was this case. Do not test a token against what a scaffolded project's seed happens