From b5fd687c2b4dfcc6d09304cf7bd54f16726901c9 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 8 Sep 2026 02:19:03 +0000 Subject: [PATCH] fix(scripts): drop both transcribed counts from the battery-roster comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The roster block's STOP paragraph named the three callees' inner sinks by shape and hung two transcribed numbers off two of them: `fixtureSelfTest`'s "`check()` helper (14 calls)" and `decisionTableSelfTest`'s "literal 8-row table". Neither is derived or compared by anything, and the first had drifted to 28 while the second was still exactly 8 — so the one block whose subject is which numbers in this file are load-bearing gave a reader no way to tell which of its own two numbers to trust. Both counts come out. The sentence's job is the contrast between three different SHAPES — a helper, a literal table with its driving loop, a bare boolean — and the counts were never carrying that; removing them also makes the three list items parallel, which they were not while two of them were sized and one was not. Comment-only. Stripping every full-line `//` from the file before and after this change yields byte-identical text, and `--self-test` prints a byte-identical transcript, so no gate's accept/reject behaviour moves. The floor is untouched and is deliberately not an assertion count: `SELF_TEST_BATTERIES` floors each callee at 1 registration. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_012GKcPZbMoGq7WPzKLfRBTU --- scripts/check-regen-pending.mjs | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/scripts/check-regen-pending.mjs b/scripts/check-regen-pending.mjs index c413dc0fc3..fea55814ac 100755 --- a/scripts/check-regen-pending.mjs +++ b/scripts/check-regen-pending.mjs @@ -837,15 +837,15 @@ const invokedDirectly = isEntrypoint(import.meta.url); // // STOP -- the three callees' own inner sinks are NOT batteries here, and they // are worth naming because all three are different shapes: `fixtureSelfTest`'s -// `check()` helper (14 calls), `decisionTableSelfTest`'s literal 8-row table -// with its driving loop, and `prePushIsArmedSelfTest`'s bare boolean. Recipe A -// (PR #15271, `check-sdui-manifest`) does make a table row a battery -- for a -// file whose SELF-TEST *is* the table: one literal table, one driving loop over -// it, one sink. Here the table is a local of ONE callee among three, and that -// callee already reduces its rows to a single returned verdict of its own. -// Flooring those rows would floor one callee's internals while the other two -// stayed at callee granularity -- a roster whose unit changes per entry. The -// rule: the battery is the unit the DISPATCH names. +// `check()` helper, `decisionTableSelfTest`'s literal table with its driving +// loop, and `prePushIsArmedSelfTest`'s bare boolean. Recipe A (PR #15271, +// `check-sdui-manifest`) does make a table row a battery -- for a file whose +// SELF-TEST *is* the table: one literal table, one driving loop over it, one +// sink. Here the table is a local of ONE callee among three, and that callee +// already reduces its rows to a single returned verdict of its own. Flooring +// those rows would floor one callee's internals while the other two stayed at +// callee granularity -- a roster whose unit changes per entry. The rule: the +// battery is the unit the DISPATCH names. // // STOP -- the TWO assertions written INLINE in the dispatch block (`noDist`, // `noTree`) are deliberately OUTSIDE this roster, and that is a DECLARED GAP,