Filed out-of-scope from #7362 (that card's file surface was content/docs/guide/agent-skills.md and, conditionally, ci-cd-pipeline.md:581 only — this is a different line, a different sentence, unassigned).
What is stale
content/docs/guide/ci-cd-pipeline.md:551, in the "Skill Guide Paths (skills-paths.yml)" section:
Runs scripts/check-skills-paths.mjs, which reads every markdown file under skills/ and asks, of each in-repo path the prose states inside a backtick code span, whether it exists on disk.
This is evergreen present-tense prose describing the script's current scan surface (not a "measured at commit X" statement like the main@6422aa891 sentence a few lines below, which #7965 already reviewed and ruled correct because it declares its measurement point). #7358 widened SCAN_ROOTS to ['skills', '.claude/skills'], so the sentence has been incomplete since then — today's real reading (node scripts/check-skills-paths.mjs) is:
✅ check-skills-paths: OK (88/89 stated path(s) resolve across 20 guide file(s); 1 baselined).
skills/ — 28/28 resolve across 16 file(s)
.claude/skills/ — 60/61 resolve across 4 file(s)
A reader who takes "reads every markdown file under skills/" literally would conclude .claude/skills/** guides (including the very console-development.md / no-touch-zones.md pair #7251 moved there) are outside this gate's reach — the exact wrong conclusion #7358 exists to prevent, and the same failure mode #7404 fixed for .github/workflows/skills-paths.yml's header comment. This is the same defect class, one file over, still open.
Why not fixed on the spot
#7362's dispatch boundary was content/docs/guide/agent-skills.md plus ci-cd-pipeline.md:581 "ONLY as the re-measured baseline truth requires" — this is a different sentence at a different line, so it's out of that claim's file surface.
Suggested fix
Name both roots, e.g. "reads every markdown file under skills/ and .claude/skills/" — two words, no numeral to go stale. scripts/__tests__/ci-cd-pipeline-doc.test.ts does not appear to pin this sentence (grepped for the surrounding tokens with no hit), so a prose edit shouldn't move any pin.
finding, no pm:queue — this is an observation for PM triage, not a defect I'm asking to be actioned on a timeline.
Filed out-of-scope from #7362 (that card's file surface was
content/docs/guide/agent-skills.mdand, conditionally,ci-cd-pipeline.md:581only — this is a different line, a different sentence, unassigned).What is stale
content/docs/guide/ci-cd-pipeline.md:551, in the "Skill Guide Paths (skills-paths.yml)" section:This is evergreen present-tense prose describing the script's current scan surface (not a "measured at commit X" statement like the
main@6422aa891sentence a few lines below, which #7965 already reviewed and ruled correct because it declares its measurement point). #7358 widenedSCAN_ROOTSto['skills', '.claude/skills'], so the sentence has been incomplete since then — today's real reading (node scripts/check-skills-paths.mjs) is:A reader who takes "reads every markdown file under
skills/" literally would conclude.claude/skills/**guides (including the veryconsole-development.md/no-touch-zones.mdpair #7251 moved there) are outside this gate's reach — the exact wrong conclusion #7358 exists to prevent, and the same failure mode #7404 fixed for.github/workflows/skills-paths.yml's header comment. This is the same defect class, one file over, still open.Why not fixed on the spot
#7362's dispatch boundary was
content/docs/guide/agent-skills.mdplusci-cd-pipeline.md:581"ONLY as the re-measured baseline truth requires" — this is a different sentence at a different line, so it's out of that claim's file surface.Suggested fix
Name both roots, e.g. "reads every markdown file under
skills/and.claude/skills/" — two words, no numeral to go stale.scripts/__tests__/ci-cd-pipeline-doc.test.tsdoes not appear to pin this sentence (grepped for the surrounding tokens with no hit), so a prose edit shouldn't move any pin.finding, nopm:queue— this is an observation for PM triage, not a defect I'm asking to be actioned on a timeline.