docs(pm): dispatch-gates residue names the unreachable-root-file class, not a specimen that became reachable

[os-warren]

Fixes#10012

renderResidue's top-level-FILE clause illustrated the unreachable class with README.md. That was honest until the doc-anchors gate declared the subtree spelling — after which the sentence offered, as its example of a population nothing can reach, the one root file in this repo that a card does derive. The rule it states is unchanged and still exactly correct; only the specimen went stale.

Took the card's recommended remedy (2), de-specimen, not (1) rename-the-specimen: a specimen is a claim about the tree this function has no way to keep true, so renaming it only resets the clock until the next declaration lands. The clause now names the class and, in the same breath, the escape hatch — which restates the rule rather than the tree and so cannot rot the same way — and points at hintCovers' docblock for the measurement.

The same specimen, repeated twice more

The card asked whoever took it to check for repeats. Two, both the same stale attribution — a root file described as out of reach by the very gate that now declares it:

• hintCovers' docblock: "a population that is a top-level FILE (README.md, ARCHITECTURE.md — the rest of check-doc-anchors' corpus)". Now says what is refused is the literal, never the file, and points at the escape hatch already sitting 15 lines below it.
• the self-test comment above the !hintCovers('README.md', 'README.md') case, which carried the identical parenthetical. Now cross-links the rootFileDeclarations cases that pin the declarations.

Both are the same defect class, mechanical, evidence-pinned by cases already in this file, and inside the same gate family — no new verification surface.

Measurements the corrected prose rests on

card surface	families derived	via
README.md	1	check:doc-anchors ⇢ gate source README.md/**
ARCHITECTURE.md	1	check:doc-anchors ⇢ ARCHITECTURE.md/**
AGENTS.md	7	six gates, all via AGENTS.md/**
LICENSE	0	—
examples/AGENTS.md	0	—

AGENTS.md/** is measured live before being cited as the escape-hatch spelling, so the replacement does not plant a fresh stale claim. LICENSE and examples/AGENTS.md are the controls: still zero, i.e. the refusal itself is intact.

Self-test: 332 → 334

Two pins added so the specimen cannot grow back. Their comment is explicit that the first holds only the literal that actually rotted and that the second — the durable half is present at all — is the load-bearing one.

Reverse verification, direction predicted in writing before running: reverting the prose turns both new pins red. Observed exactly that, EXIT=1:

 x the residue names no repo-root file as an unreachable specimen
x and states the escape hatch instead, which restates the rule and cannot rot
x dispatch-gates self-test: 2 of 334 case(s) failed.

Restore leg re-run: 334 cases pass, tree clean. No rebuild applies to either leg — dispatch-gates.mjs is executed directly by node from source, with no dist/ in the resolution path.

Gates, on the final commit cd43ab4e0

Union re-derived from the real diff (node scripts/pm/dispatch-gates.mjs, no args) on the committed tree, each verdict line quoted from the gate itself, exit codes captured before any pipe:

• pnpm check:pm-dispatch-gates — dispatch-gates self-test: 334 cases pass.
• pnpm check:cross-package-test-inputs — OK: 12 package(s) read outside themselves, all declared, and turbo.json hashes every declared glob.
• pnpm check:nul-bytes — check-nul-bytes: OK (scanned 6347 text file(s) -- 6347 tracked, 0 untracked-not-ignored; skipped 5 binary; no raw ASCII control bytes).

Prose and self-test only, nothing published: skip-changeset.

---

Generated by Claude Code