Files
ersatztv/docs/decisions/records/testing
timothy e3a3c46f1d fix(819): pin the round-6 mechanism, and stop the Docker stage dropping 117 files
Round 7 found no blocker and reported the cancellation class terminated for
every single-site edit it could construct — 16 mutations, all caught. What it
found instead was proof debt on the round-6 fix itself, plus two environment
defects.

- The `others` term of the new cross-check had no clause proof. MEASURED:
  removing it left all 1265 tests green, because `others` is EMPTY on any clean
  checkout — the only tree CI sees — and with it gone an ordinary untracked
  scratch file reddens the developer's checkout while CI stays green. That is
  the #778/#806 shape #819 exists to remove, reintroduced by #819's own fix.
  Extracted as `unaccountedWalkedPaths` and pinned by fixtures, the load-bearing
  case being "in `others` only -> not returned".
- The anti-vacuity floor shipped as TWO identical assertions side by side, so
  deleting either left the suite green — `duplicate guards mask each other`,
  and the comment claimed a clause proof that measurement refuted. One
  assertion now, over `populationIsDegenerate`, with a four-case fixture table.
  MEASURED: `return false` now reddens by name; before, it was green.
- The new real-git tests were not hermetic: MEASURED 2 failures under a global
  `commit.gpgsign = true`, which many people set. The commit was unnecessary —
  `ls-files` reads the INDEX — so the fixture now stages without committing, and
  the non-repo test pins `GIT_CEILING_DIRECTORIES` so it does not depend on
  where TMPDIR points. Green under both configurations.
- The cross-check's message named one cause and MEASURED two more: a disk/index
  spelling divergence (where the sibling test gives the better diagnosis) and an
  untracked NESTED git repository, which `ls-files --others` reports as a
  directory rather than as files. Both named now, and a trailing-slash `others`
  entry covers its subtree so an embedded repo is not a permanent spurious red.
- The Dockerfile threw away 117 test files (~1228 tests) that run fine gitless
  in order to accommodate one that cannot. It now excludes that single file
  instead. MEASURED in an exact gitless replica: 117 files / 1228 tests pass,
  lint, typecheck and build all exit 0.

Residuals, now three rather than two: the surviving hole is a two-site PARTITION
inside the derivation — moving paths out of `tracked` and into `others` preserves
the union the cross-check compares, so it is invisible to any consumer. MEASURED
green with a planted call site. Nothing a consumer can compute closes it; a
derivation that lies consistently in both outputs is answerable only by testing
the derivation, which is what the real-git tests are for. Stated in the guard, in
`docs/guard-inventory.md` and in the record rather than left implied.

Also: the plugin deduplicates `tracked` (a merge conflict emits an unmerged path
once per stage), its error message drops the "guards" plural retracted earlier
elsewhere, `vite-env.d.ts` records that it is a hand-written mirror with no
compile-time link, the record's enumeration was four items for five rounds
(round 2's shared scope was missing), and the last undated "previous head"
references are now issue-referenced.

Refs: #819
Decisions-Edit: yes
2026-08-29 05:12:23 +02:00
..