Filed unassigned and bare by the domain:cli execution seat while running the derived gate union for another card. ⛔ Not graded here and no domain:* set — that is triage's field.
The measurement
pnpm check:docs-audit-scope fails on origin/main, before its real check ever runs, on its own self-test:
> node scripts/docs-audit/affected-docs.mjs --self-test && node scripts/docs-audit/check-audit-scope.mjs --self-test && node scripts/docs-audit/check-audit-scope.mjs
✗ self-test "every contract declaration admitted is a packages/spec API declaration": kind=contract → expected scanRouteSurface=true, got false
✗ affected-docs self-test failed (1 case(s)).
ELIFECYCLE Command failed with exit code 1.
The chain short-circuits on the first &&, so check-audit-scope.mjs — the part that judges the tree — never runs at all. Whatever that gate is supposed to assert about docs-audit scope, nothing is asserting it today.
Why this is not the reporting seat's change
The seat that found it was editing packages/cli, content/docs, turbo.json, .changeset, .github/workflows and two scripts/*.mjs files, none of them under scripts/docs-audit/. Both sources the self-test runs are byte-identical to the branch point:
| file |
blob at branch point 4f85e4d11 |
blob in the working tree |
scripts/docs-audit/affected-docs.mjs |
a41faf9c27433c54c78270acbc0720c5df55b97d |
a41faf9c27433c54c78270acbc0720c5df55b97d |
scripts/docs-audit/check-audit-scope.mjs |
60debd41a356eb7be3cb6616ad02835a99946651 |
60debd41a356eb7be3cb6616ad02835a99946651 |
And git diff --name-only 4f85e4d11 origin/main -- scripts/docs-audit/ is empty, so the same two blobs are what origin/main carries right now. The red is the tree's, not a branch's.
The lead, not a diagnosis
The named case is about kind=contract admission, and the most recent commit touching affected-docs.mjs is e77635b8fda — "refactor(docs-audit): a route SOURCE of two kinds — admit spec contract declarations behind a runtime-registration guard (#15274)". That change is about exactly the property the failing case names, which makes it the first place to look; ⛔ this seat did not read it and is not asserting it is the cause.
Why it is worth a card rather than a shrug
A gate whose self-test refuses is not a gate that found something — it is a gate that stopped measuring, and this one is wired so that the refusal also cancels the real check behind it. It exits 1, which reads like an ordinary finding, so a reader who does not open the log will look for a docs-scope problem in their own diff that is not there.
Filed unassigned and bare by the
domain:cliexecution seat while running the derived gate union for another card. ⛔ Not graded here and nodomain:*set — that is triage's field.The measurement
pnpm check:docs-audit-scopefails onorigin/main, before its real check ever runs, on its own self-test:The chain short-circuits on the first
&&, socheck-audit-scope.mjs— the part that judges the tree — never runs at all. Whatever that gate is supposed to assert about docs-audit scope, nothing is asserting it today.Why this is not the reporting seat's change
The seat that found it was editing
packages/cli,content/docs,turbo.json,.changeset,.github/workflowsand twoscripts/*.mjsfiles, none of them underscripts/docs-audit/. Both sources the self-test runs are byte-identical to the branch point:4f85e4d11scripts/docs-audit/affected-docs.mjsa41faf9c27433c54c78270acbc0720c5df55b97da41faf9c27433c54c78270acbc0720c5df55b97dscripts/docs-audit/check-audit-scope.mjs60debd41a356eb7be3cb6616ad02835a9994665160debd41a356eb7be3cb6616ad02835a99946651And
git diff --name-only 4f85e4d11 origin/main -- scripts/docs-audit/is empty, so the same two blobs are whatorigin/maincarries right now. The red is the tree's, not a branch's.The lead, not a diagnosis
The named case is about
kind=contractadmission, and the most recent commit touchingaffected-docs.mjsise77635b8fda— "refactor(docs-audit): a route SOURCE of two kinds — admit spec contract declarations behind a runtime-registration guard (#15274)". That change is about exactly the property the failing case names, which makes it the first place to look; ⛔ this seat did not read it and is not asserting it is the cause.Why it is worth a card rather than a shrug
A gate whose self-test refuses is not a gate that found something — it is a gate that stopped measuring, and this one is wired so that the refusal also cancels the real check behind it. It exits 1, which reads like an ordinary finding, so a reader who does not open the log will look for a docs-scope problem in their own diff that is not there.