chore: address Copilot review round 9

- Enrol both skill gates in the repo's gate-integrity vouch cycle. A gate that
  stops being invoked fails silently with every fixture test green, which is the
  failure the existing cycle exists to prevent. `verify:format-coverage` now
  vouches for `verify:skills`, `verify:skills` vouches back, and it additionally
  asserts the two links nothing else could see: `verify:skills:cli` present in
  `local:gate` and in the workflow — neither is reachable from `validate` or
  from any test. `checkWiring` is pure and unit-tested, with a live case against
  the real package.json and workflow so the fixtures cannot drift. All four
  links verified by mutation.
- The existing sibling-vouch fixture is now a table over every sibling, so
  adding a fourth guard later does not need a new test.
- release skill: stop hard-coding `2.3.0`, which has already shipped — the tag
  command aborted on an existing tag and the branch template named the wrong
  release. Both now read the version from `package.json` (the tag from
  `origin/main`'s), with a warning never to copy a version out of the file.

Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-08-29 03:04:03 -04:00
commit 17068fc89e

View file

@ -31,6 +31,7 @@ import { spawnSync } from "node:child_process";
import path from "node:path";
import { fileURLToPath } from "node:url";
import { claudeSpawnArgs, probeClaudeVersion } from "./lib/claude-cli.mjs";
import { reachableScripts, rootReachesScript } from "./lib/npm-scripts.mjs";
import {
compareVersions,
parseClaudeVersion,
@ -58,6 +59,41 @@ export function skillDirs(
.sort();
}
/**
* Assert the two skill gates are still WIRED, not merely present.
*
* A gate that stops being invoked fails silently and every fixture test stays
* green — which is the same failure the sibling guards' vouch cycle exists to
* prevent, so this joins it (Copilot). Two distinct links:
*
* - `verify:skills` (this file) must be reachable from the root `validate`.
* It cannot detect its own absence, so `verify:format-coverage` vouches for
* it and this vouches back — the established cycle.
* - `verify:skills:cli` must be in `local:gate` AND in the workflow. That is
* the step that actually runs the authoritative validator, and it is
* reachable from neither `validate` nor any test, so nothing else would
* notice it going missing.
*/
export function checkWiring(rootScripts, workflowText) {
const problems = [];
if (!rootReachesScript(rootScripts, "verify:format-coverage")) {
problems.push(
"the root `validate` no longer runs `verify:format-coverage` (a sibling guard). Restore it.",
);
}
if (!reachableScripts(rootScripts, "local:gate").has("verify:skills:cli")) {
problems.push(
"`npm run local:gate` no longer runs `verify:skills:cli`, so the authoritative validator never runs locally. Restore it.",
);
}
if (!/npm run verify:skills:cli/.test(workflowText)) {
problems.push(
"`.github/workflows/main.yml` no longer runs `npm run verify:skills:cli`, so the authoritative validator never runs in CI. Restore it.",
);
}
return problems;
}
function main(argv = process.argv.slice(2)) {
// An explicit directory is the seam the fixture tests drive; without it this
// guard could only ever be exercised against the repo's own (green) skills,
@ -66,6 +102,20 @@ function main(argv = process.argv.slice(2)) {
const SKILLS_DIR = override ? path.resolve(override) : DEFAULT_SKILLS_DIR;
const failures = [];
// Only meaningful against the real repo; a fixture run has no wiring.
if (!override) {
const rootScripts = JSON.parse(
readFileSync(path.join(ROOT, "package.json"), "utf8"),
).scripts;
const workflow = readFileSync(
path.join(ROOT, ".github", "workflows", "main.yml"),
"utf8",
);
for (const problem of checkWiring(rootScripts, workflow)) {
failures.push(problem);
}
}
if (!existsSync(SKILLS_DIR)) {
console.error(
`verify:skills — ${path.relative(ROOT, SKILLS_DIR)} does not exist.`,