Files
ersatztv/web/vite-plugins
timothy e08df757e7 fix(819): correct the fail-direction claim — residual (3) is BLIND, not noisy
Round 10 adjudicated the wiring disagreement in the previous commit's favour
(round 9's proposed assertions are green against both mutations; the structural
argument holds), found no blocker and no HIGH, and then found that the previous
commit had introduced a measured falsehood while writing that argument down.

"Both (3) and (4) are fail-noisy" is false for (3). MEASURED, and reproduced here
before fixing: a union-preserving mispartition in the plugin — move
`src/components/` out of `tracked` and append it to `others` — hides a planted
`pageSize: 100` in `src/components/bugPreview.tsx` with the whole suite green
(43/43), where the same plant without the mutation reddens with `UNREGISTERED
(1)`. Round 7 had already measured this and I wrote the opposite anyway.

Why it matters more than a wording slip: fail-DIRECTION is the entire argument
for tolerating a residual rather than closing it. A reader deciding whether (3)
deserves work would have read "cannot hide a call site" — which is exactly the
inference this issue exists to prevent. Two neighbouring sentences contradicted
it in the same file, which is how it survived my own read.

The residual list now states five, with their directions separated: (1), (2), (4)
and (5) are fail-noisy — they redden a checkout and cannot hide a call site —
while (3) is blind, tolerated only because nothing a CONSUMER computes can see it
(the union it compares is unchanged), and answered by testing the derivation
directly. The real-git tests that answer it catch an unconditional mispartition,
not one keyed on a path pattern, and now say so.

Also from round 10:
- The list said "Three residuals" and enumerated four; `ABSENT_FROM_DISK` was a
  fifth, documented only at its declaration. Five, listed.
- "No assertion can tell which is passed" was broader than measured: a
  `listSourceFiles.toString()` assertion DOES redden one of the two mutations. It
  is rejected rather than impossible — a text snapshot of one's own source is the
  hand-written-mirror shape this file spent nine rounds removing, and it misses
  the other mutation. Both places now say "no assertion comparing the two
  populations", with the reason.
- The cross-check message said the shortfall test is "above"; it is below. This
  branch's own sweep of stale directional pointers missed it.
- "Excluded for DIFFERENT reasons" survived above the text retracting exactly
  that framing. The reasons OVERLAP — both files need the binary, one also needs
  a checkout — and reading them as separate is what produced the round-8 blocker.
- `vite-env.d.ts` claimed a renamed field always fails loudly; true for `tracked`
  and `others`, silent for `absentFromDisk`.
- The realgit non-repo test asserts a message the missing-binary path also emits,
  so it passes for the wrong reason where git is absent — recorded, since that is
  the environment the file is excluded from.
- A blank line had made the guard-inventory scope list render loose.

Refs: #819
2026-08-29 06:19:46 +02:00
..