Skip to content

Commit bbd5e22

Browse files
committed
refactor(check-type-check-coverage): the ANTI-content failure line no longer claims a cause it cannot know
Every `absent` needle failed with "which is the other ledger's remedy". That was true while the only anti-content assertions were cross-ledger ones; the TEST_DEBT case now pins a route this gate withdrew rather than another ledger's advice, and the sentence read false on exactly the four failures the withdrawal's ablation produces. The line now states what the case pins and leaves the cause to each case's own `why`, which already carries it. Claude-Session: https://claude.ai/code/session_017ef78bLdybu3AffehKkhfk Co-authored-by: Claude <noreply@anthropic.com>
1 parent 0a40611 commit bbd5e22

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎scripts/check-type-check-coverage.mjs‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6469,8 +6469,8 @@ function selfTest() {
64696469
for (const needle of c.absent) {
64706470
if (c.message.includes(needle))
64716471
failures.push(
6472-
`#11491 graduation remedy — ${c.label}: message STILL contains ${needle}, which is the other `
6473-
+ `ledger's remedy. ${c.why}`,
6472+
`#11491 graduation remedy — ${c.label}: message STILL contains ${needle}, which this case pins `
6473+
+ `as ABSENT -- another ledger's remedy, or a route this one no longer offers. ${c.why}`,
64746474
);
64756475
}
64766476
}

0 commit comments

Comments
 (0)