You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed while re-measuring lint.yml's swallow-census comment block for #15569.
That card's ruling holds the change to lint.yml and explicitly does not touch
the census script, so the same stale arithmetic INSIDE the instrument is filed
here instead.
The reading
scripts/measure-durability-swallow-family.mjs's own usage header:
scripts/measure-durability-swallow-family.mjs:10 // ... --self-test # all 4 control families
scripts/measure-durability-swallow-family.mjs:11 // node scripts/measure-durability-swallow-family.mjs --self-test=gated
scripts/measure-durability-swallow-family.mjs:12 // # the 3 families CI runs
What the same file declares today, read from the self-test body and from the
verdict line it prints (lines 2102-2117):
POSITIVE_CONTROLS, NEGATIVE_CONTROLS, REGRESSION_CONTROLS, RESOLUTION_CONTROLS -- the original four;
That is SEVEN declared, and --self-test=gated runs SIX of them -- the loop is for (const control of gated ? [] : POSITIVE_CONTROLS), so POSITIVE is the only
family the gated mode drops. The header says four and three.
Same defect class as #15569, one level in: a documented count that the file's
own verdict line contradicts on every CI run. The header is what a reader reaches
for first when deciding which mode to invoke, so the wrong count is load-bearing
for that choice.
Suggested shape, not a prescription
#15569's ruling asked for the count to be written as a NAMED list rather than a
bare integer, so that the next family added contradicts a list instead of an
integer; the same treatment fits here. Whether the header should instead point at SELF_TEST_MODES and carry no count at all is the open question.
Re-check
sed -n '1,13p' scripts/measure-durability-swallow-family.mjs
sed -n '2102,2118p' scripts/measure-durability-swallow-family.mjs
grep -n 'gated ? \[\] : POSITIVE_CONTROLS' scripts/measure-durability-swallow-family.mjs
⛔ NOT MEASURED by running it: pnpm check:swallow-census-controls is exit 1 with ERR_MODULE_NOT_FOUND: Cannot find package 'typescript' on the box this was read
from, so the verdict line above is quoted from the source that BUILDS it, not
from a run. The count itself is a static reading of the declarations and does not
depend on the run.
Duplicate check: 617 open items (584 issues) enumerated by page over the
repo-scoped REST list endpoint and grepped locally for measure-durability-swallow-family near the family counts and for
swallow-family header prose; control word exactly ONE hint verified to hit
exactly the card it should (#15537) and nothing else. REST search/issues is 403
in this session, so the list endpoint was the channel. No match.
Noticed while re-measuring
lint.yml's swallow-census comment block for #15569.That card's ruling holds the change to
lint.ymland explicitly does not touchthe census script, so the same stale arithmetic INSIDE the instrument is filed
here instead.
The reading
scripts/measure-durability-swallow-family.mjs's own usage header:What the same file declares today, read from the self-test body and from the
verdict line it prints (lines 2102-2117):
POSITIVE_CONTROLS,NEGATIVE_CONTROLS,REGRESSION_CONTROLS,RESOLUTION_CONTROLS-- the original four;DETERMINEDregister cross-check, asserted in BOTH modes since [finding] the #12981 census prints 5 DARK sites as "the repair worklist" when 4 are settled determinations — an annotation cannot move a site out of the bucket #13886;(PR docs(scripts): the swallow-family census reads the #12981 handover as landed, and cross-checks its copy of the gate vocabulary (#15459, #15473) #15502);
WORKLIST_READING_CONTROLS, asserted in BOTH modes, added by [finding] the swallow-family census's empty-worklist line still calls the #12981 gate handover "unblocked" after that handover landed #15503.That is SEVEN declared, and
--self-test=gatedruns SIX of them -- the loop isfor (const control of gated ? [] : POSITIVE_CONTROLS), so POSITIVE is the onlyfamily the gated mode drops. The header says four and three.
Same defect class as #15569, one level in: a documented count that the file's
own verdict line contradicts on every CI run. The header is what a reader reaches
for first when deciding which mode to invoke, so the wrong count is load-bearing
for that choice.
Suggested shape, not a prescription
#15569's ruling asked for the count to be written as a NAMED list rather than a
bare integer, so that the next family added contradicts a list instead of an
integer; the same treatment fits here. Whether the header should instead point at
SELF_TEST_MODESand carry no count at all is the open question.Re-check
⛔ NOT MEASURED by running it:
pnpm check:swallow-census-controlsis exit 1 withERR_MODULE_NOT_FOUND: Cannot find package 'typescript'on the box this was readfrom, so the verdict line above is quoted from the source that BUILDS it, not
from a run. The count itself is a static reading of the declarations and does not
depend on the run.
Duplicate check: 617 open items (584 issues) enumerated by page over the
repo-scoped REST list endpoint and grepped locally for
measure-durability-swallow-familynear the family counts and forswallow-family header prose; control word
exactly ONE hintverified to hitexactly the card it should (#15537) and nothing else. REST
search/issuesis 403in this session, so the list endpoint was the channel. No match.
Unassigned, unlabeled -- for PM triage.
Generated by Claude Code