ci(skill-check): scan the docs a contributor reads #229

Merged

logan merged 3 commits from docs/220-skill-check-scope into main 2026-09-03 17:35:40 +00:00

Conversation 1 Commits 3 Files Changed 4

+30 -9

3 Commits

Author	SHA1	Message	Date
logan	b1368bbc7e	Merge remote-tracking branch 'origin/main' into docs/220-skill-check-scope	2026-09-03 13:20:23 -04:00
logan	9432f68c8b	Merge remote-tracking branch 'origin/main' into docs/220-skill-check-scope	2026-09-03 13:04:17 -04:00
logan	26251badda	ci(skill-check): scan the docs a contributor reads ... The check asserts that every make target named in a doc exists, and its scanned set was .pi/ plus CLAUDE.md. Since #50, CONTRIBUTING.md is the document a *human* goes to for a build command, and it names 21 targets that nothing verified; README.md names none today and is in for the same reason. The script's own header sentence is the argument — a renamed target sends a person off the same cliff it sends an agent off. The file list is now one `docs` variable used twice, because the failure message carried a second copy of it and a second list is a second thing to forget. The `[ -d .pi ]` guard went with it: gating the whole run on .pi/ would make the human-facing half conditional on the agent-facing one, and an empty list is the same "nothing to scan" exit without the coupling. The lefthook glob is that scanned set now rather than {Makefile,.pi/**/*.md} — #220's smaller half, and it did not fire on CLAUDE.md either, which the script had read for months. Verified by planting a bad target rather than by reading the diff: both matched forms in each of the four scanned surfaces, each naming the right file; the same two plants pass on the pre-change script; unfenced prose still does not match; and the hook fires on a staged CONTRIBUTING.md under the new glob where the old one skipped it. The count is unchanged at 47 — the set is a union — so coverage is the only thing that moved. Closes #220	2026-08-28 03:38:28 -04:00