Round 13 found no blocker. Two things, both mine.
WATCH MODE (residual 6), present since the first commit on this branch and
missed by twelve rounds. The virtual module has no backing file, so Vite never
invalidates it and `resolveTrackedSourceFiles` runs once per dev-server lifetime
while the glob refreshes. MEASURED under `npx vitest --watch`: create an
untracked scratch file mid-session and the cross-check reddens; `git add` does
not clear it; `npx vitest run` on the same tree is green. That is the #778/#806
developer-red / CI-green symptom this change exists to remove, appearing under
the invocation `docs/testing.md` documents as `npm test`.
My first probe of this reported all-green and was WRONG — a filtered watcher
never re-ran, so I was reading a stale first result. Re-measured with a forced
re-run, the review's report reproduces exactly.
The obvious fix is rejected on MEASUREMENT rather than taste, which is the part
worth recording: invalidating the module from `configureServer` on the watcher's
`add`/`unlink` does fix the scratch-file red — and then `git add`, which touches
no file and so fires no watcher event, leaves the module holding its pre-staging
answer. Measured with that hook in place, a tracked planted `pageSize: 100` goes
UNSEEN, green. It trades a noisy red for a blind green. So it is named, with both
measurements, in the guard, in `docs/guard-inventory.md` and beside the `npm test`
line in `docs/testing.md`.
Also: widening residual (3) to the plugin's three outputs last round did not
carry to its DIRECTION paragraph, which still said "(3) is invisible to any
CONSUMER by construction". Measured false for the `absentFromDisk` half — the
assertion added last round catches it wherever it overlaps a walked file — and
`docs/guard-inventory.md` already had the correct wording, so the claim had
drifted between two copies again. Corrected, with a note not to delete that
assertion as decoration.
Two smaller ones: "an UNCONDITIONAL mispartition" became the wrong noun once (3)
covered three outputs, and "the walk set and the index set are THE SAME SET" is
imprecise — they agree on every in-scope key, but the index also carries `.css`.
Refs: #819