Filed unassigned. Small, but it is the kind of stale cross-reference that reads as authoritative to the next person who greps for the name.
scripts/check-ratchet-remedy-authority.mjs records, in its why for check-doc-authoring.mjs:
Carries no ratchet at all. ROOTS, SKIP_PATHS, SKIP_FILES and GENERATED_SKILL_ARTIFACTS are declarations of what the two corpus rules read and what is generated rather than authored; each is path-scoped, and none is offered to the author as something to widen. […]
The GENERATED_SKILL_ARTIFACTS constant is removed by the PR for #11930 — it was the by-path exemption for the generated references/_index.md / references/react-blocks.md artifacts, and it existed only because those files still carried issue-ids projected from packages/spec TSDoc. With the sources stripped, the exemption guarded a clean surface, so it goes rather than being narrowed.
The gate itself does not break: it was run against the change and stays green, because its excluded verdict rests on the remaining declarations (ROOTS, SKIP_PATHS, SKIP_FILES) and nothing parses the why string against the file. So this is prose accuracy, not a red — which is exactly why it will otherwise sit there indefinitely.
The fix
Drop GENERATED_SKILL_ARTIFACTS from that sentence. The rest of the entry stays correct as written, including its closing line — "Its published-catalog id rule reached this corpus by first shipping a per-passage allowlist and being turned red here for offering it […] If this flips, that list came back." — which is about the per-passage allowlist, a different thing, and is unaffected.
Ordering
Blocked-by: — this should ride whichever lands second of:
Editing the file from the #11930 lane would have raced #12061's claim on it, so it was deliberately left. If #12061 rewrites that entry wholesale, check whether this is already moot before doing anything.
Filed unassigned. Small, but it is the kind of stale cross-reference that reads as authoritative to the next person who greps for the name.
scripts/check-ratchet-remedy-authority.mjsrecords, in itswhyforcheck-doc-authoring.mjs:The
GENERATED_SKILL_ARTIFACTSconstant is removed by the PR for #11930 — it was the by-path exemption for the generatedreferences/_index.md/references/react-blocks.mdartifacts, and it existed only because those files still carried issue-ids projected frompackages/specTSDoc. With the sources stripped, the exemption guarded a clean surface, so it goes rather than being narrowed.The gate itself does not break: it was run against the change and stays green, because its
excludedverdict rests on the remaining declarations (ROOTS,SKIP_PATHS,SKIP_FILES) and nothing parses thewhystring against the file. So this is prose accuracy, not a red — which is exactly why it will otherwise sit there indefinitely.The fix
Drop
GENERATED_SKILL_ARTIFACTSfrom that sentence. The rest of the entry stays correct as written, including its closing line — "Its published-catalog id rule reached this corpus by first shipping a per-passage allowlist and being turned red here for offering it […] If this flips, that list came back." — which is about the per-passage allowlist, a different thing, and is unaffected.Ordering
Blocked-by:— this should ride whichever lands second of:skills/**artifacts — their source ispackages/specTSDoc, so the ruled strip could not reach them #11930 (removes the constant), andscripts/check-ratchet-remedy-authority.mjsitself and is marked blocked on a recorded verdict.Editing the file from the #11930 lane would have raced #12061's claim on it, so it was deliberately left. If #12061 rewrites that entry wholesale, check whether this is already moot before doing anything.