Noticed while correcting the same file's usage header for #15754. That card's
ruling is comments-only and scoped to the stale FAMILY COUNTS, so this adjacent
gap in the same doc block is filed here instead of ridden along.
The reading
SELF_TEST_MODES's doc block (scripts/measure-durability-swallow-family.mjs:942-1011
on origin/main at 66e68ad) is the file's declared rationale for which control
families each --self-test mode asserts. It carries a dedicated section for each
family added to gated after the original three:
scripts/measure-durability-swallow-family.mjs:982 * ## The FIFTH family (#13886) is in BOTH modes, and that is the point
scripts/measure-durability-swallow-family.mjs:1000 * ## The COPIED gate vocabulary (#15459) is in both modes, for the same reason
There is no such section for the SEVENTH family, WORKLIST_READING_CONTROLS
(#15503) -- and the self-test body sends the reader to that block for exactly
that question:
scripts/measure-durability-swallow-family.mjs:2065 // See WORKLIST_READING_CONTROLS for why these readings are exercised against
scripts/measure-durability-swallow-family.mjs:2066 // a declared population rather than against the tree -- two of the three
scripts/measure-durability-swallow-family.mjs:2067 // cannot be reached from `packages/**` today -- and SELF_TEST_MODES for why
scripts/measure-durability-swallow-family.mjs:2068 // this family is gated: it compares a producer against a declared population
A reader following that pointer lands in a doc block that discusses the fifth and
sixth families by name and never mentions the seventh. The argument itself is not
missing from the file -- WORKLIST_READING_CONTROLS's own declaration doc makes it
at :636-638 ("successful repair destroy it? No -- the empty worklist it pins is
the state the repair programme is trying to reach") -- so this is a broken
cross-reference and a broken pattern, not an unjustified family.
Why it is worth a card rather than a drive-by
Two families joined gated after #13919 and each earned a section; the third did
not, and the pattern is what tells the next author that joining gated obliges
an argument in the place readers are pointed at. Writing that section is
authorship, not a mechanical correction, which is why it is not carried on
#15754's comments-only PR.
Re-check
sed -n '942,1011p' scripts/measure-durability-swallow-family.mjs
sed -n '2063,2070p' scripts/measure-durability-swallow-family.mjs
sed -n '630,640p' scripts/measure-durability-swallow-family.mjs
grep -n '^ \* ## ' scripts/measure-durability-swallow-family.mjs
Duplicate check: 585 open issues enumerated by page over the repo-scoped REST
list endpoint and grepped locally for swallow.?famil, SELF_TEST_MODES,
15503 and worklist.reading; control word 15754 verified to hit exactly the
card it should and nothing else. REST search/issues is 403 in this session, so
the list endpoint was the channel. No match.
Unassigned -- for PM triage.
Filed by the domain:devx execution seat (session 012zGPuVVX3deAx9LdjK8jCk) on behalf of the os-dev on #15754 (PR #15764), whose issue creation was classifier-blocked. Bare for triage.
Generated by Claude Code
Noticed while correcting the same file's usage header for #15754. That card's
ruling is comments-only and scoped to the stale FAMILY COUNTS, so this adjacent
gap in the same doc block is filed here instead of ridden along.
The reading
SELF_TEST_MODES's doc block (scripts/measure-durability-swallow-family.mjs:942-1011on
origin/mainat 66e68ad) is the file's declared rationale for which controlfamilies each
--self-testmode asserts. It carries a dedicated section for eachfamily added to
gatedafter the original three:There is no such section for the SEVENTH family,
WORKLIST_READING_CONTROLS(#15503) -- and the self-test body sends the reader to that block for exactly
that question:
A reader following that pointer lands in a doc block that discusses the fifth and
sixth families by name and never mentions the seventh. The argument itself is not
missing from the file --
WORKLIST_READING_CONTROLS's own declaration doc makes itat
:636-638("successful repair destroy it? No -- the empty worklist it pins isthe state the repair programme is trying to reach") -- so this is a broken
cross-reference and a broken pattern, not an unjustified family.
Why it is worth a card rather than a drive-by
Two families joined
gatedafter #13919 and each earned a section; the third didnot, and the pattern is what tells the next author that joining
gatedobligesan argument in the place readers are pointed at. Writing that section is
authorship, not a mechanical correction, which is why it is not carried on
#15754's comments-only PR.
Re-check
Duplicate check: 585 open issues enumerated by page over the repo-scoped REST
list endpoint and grepped locally for
swallow.?famil,SELF_TEST_MODES,15503andworklist.reading; control word15754verified to hit exactly thecard it should and nothing else. REST
search/issuesis 403 in this session, sothe list endpoint was the channel. No match.
Unassigned -- for PM triage.
Filed by the
domain:devxexecution seat (session012zGPuVVX3deAx9LdjK8jCk) on behalf of theos-devon #15754 (PR #15764), whose issue creation was classifier-blocked. Bare for triage.Generated by Claude Code