Files
ersatztv/web
timothy 5ebfe76688 fix(819): close the fattened-absentFromDisk hole, and retract a third false coverage claim
Round 12 found a BLOCKER, and it is the third instance of one habit of mine in
this change: an affirmative coverage claim I had not measured. The guard said

  "Every mutation that could make it blind runs through `expectedTrackedSources`,
   which the fixture test pins."

MEASURED FALSE, and reproduced here before fixing. Widening the plugin's own
derivation by `|| path.startsWith('src/components/')` does not run through that
function at all — the fixture test INJECTS `absentFromDisk`, so it structurally
cannot police what the plugin derives. Those files are then subtracted from
`expected`, which disarms the hole-detection direction: a tracked
`src/components/.probe819.ts` holding `pageSize: 100` goes from red — named
correctly by the shortfall test — to 43/43 green.

The co-occurring condition is not exotic. It is exactly the case the shortfall
test exists for and that this repo has measured as PERMANENT rather than
transient: a dotfile, a dot-directory, or a disk/index spelling divergence under
`core.ignorecase` (true on this machine) or NFD/NFC.

CLOSED rather than merely stated, since one assertion does it: a path the WALK
found is on disk by construction, so it can never legitimately be reported
absent. MEASURED green on a clean tree, and red by name under the mutation.

What that closes and what it does not, measured both ways and written down: it
catches any fattening overlapping a walked file. A fattening restricted to paths
the walk cannot see anyway stays inside residual (3) — which is widened from "the
plugin's two lists partition faithfully" to "the plugin's THREE outputs describe
the repository faithfully", since `absentFromDisk` is an output the pair-shaped
wording did not cover.

Also from round 12:
- A pointer said "see residual (3)" as though it were the only blind one; (1)
  became blind last round.
- "every extra path is tracked" is inexact on a developer checkout — an untracked
  out-of-scope file lands in `others`, so it is accounted for but not tracked.
  The conclusion holds; the reason is now stated exactly.

Refs: #819
2026-08-29 07:45:56 +02:00
..
2026-07-07 10:05:39 +02:00
2026-07-02 18:36:56 +02:00
2026-07-07 10:05:39 +02:00