diff --git a/.github/workflows/ci-cd.yml b/.github/workflows/ci-cd.yml index b238560b..4afbc715 100644 --- a/.github/workflows/ci-cd.yml +++ b/.github/workflows/ci-cd.yml @@ -482,7 +482,7 @@ jobs: - name: Execute the board's recorded validationCommands (report mode) run: node .harness/scripts/ci/41-validate-evidence-commands.mjs --execute --verbose - # Ratchet, not a cliff. The budget is 38, which is what THIS RUNNER counts. + # Ratchet, not a cliff. The budget is 19, which is what THIS RUNNER counts. # # It was briefly lowered to 303 on the strength of the guard's computed # "ratchet basis" — 288 dead locally plus 15 that resolve only through @@ -493,47 +493,27 @@ jobs: # first place, and I broke it by trusting a derived figure over a measured # one. # - # 305 -> 304 obeying that rule rather than working around it. Five closure - # records (GT-424/621/629/630/632) quoted their self-test as - # `node --test 34-check-skill-registry-parity.test.mjs`, with no directory, - # while naming the real `.harness/scripts/ci/` path in the same record's - # `files` list — evidence pointing at something real through a command that - # cannot run. Repairing the five took the count to 304, and THIS JOB printed - # `304 dead (budget 305)` in run 30498743635 before the budget moved. The - # local count agreed, and that agreement is not what authorises this: the - # printed line is. - # - # 304 -> 40, the same way. 264 of the 304 were ONE event: the `src/` refactor - # moved every workspace and the closure evidence kept quoting the old layout. - # Migrating it — rewriting only where the same artifact moved and the new - # target was verified to exist — took the count to 40, and THIS JOB printed - # `40 dead (budget 304)` in run 30500947483 before the budget moved. - # - # The 40 that remain are not path rot and must not be "repaired" into - # silence: 15 reference the vendored, gitignored `.harness/bin/opa`; 4 name a - # script that was ABSORBED into 04-check-bilingual-parity rather than moved, - # so repointing them would claim a command nobody ran; 6 name artifacts that - # were deleted; 5 are root-level `npm test` recorded without the workspace - # they ran in; 2 are valid `pnpm`/`yarn info` this guard mis-parses as npm; - # the rest are build output and prose the extractor reads as commands. - # - # Two of those are guard limitations rather than evidence defects, and fixing - # them is the next real move: the npm-script parser should skip a flag's - # VALUE (`npm run --workspace