From green to accounted: what a test receipt needs to say
A falsifiable reading of commit 31fc3b4, with current CI state kept separate from source inspection.
On 1 November 2026, Revia's public main advanced to 31fc3b4, adding a versioned report for the tracked Node test runner. The useful change is not another green number; it is a sharper account of which files were supposed to run and what actually happened.
Four populations, four different questions
intended is the test path set in the checked-out index. discovered is the regular test files found under the test tree. selected is the full set or an explicitly validated subset. executed contains only selected children that emitted a non-empty JUnit test count. Per-child records preserve process status, signal, test count and terminal outcome. A subset can have exit status zero while remaining incomplete.
The report also binds a source revision, checkout cleanliness, fixture and command descriptions, the combined JUnit log digest and a canonical report digest. Those digests help detect inconsistency; they are not signatures or an authenticity root. The public contract says the GitHub workflow/job/artifact association supplies the external link to the checked-out commit.
What remains to be challenged
The commit is on public main, but its Source, Linux x64 and Windows x64 Actions are still running as of publication. This article does not call those checks passed or promote the change into a release. The repository remains research/preview: not Stable V1.0 and not production-ready.
A useful independent audit starts from a fresh clone and tries an extra discovered-only test, an empty population, a missing JUnit report, a missing child exit status, a signaled child, a failing child and an explicit subset. Pair those with a clean full-population control. For every case, compare the JSON populations, child terminal states, JUnit bytes and final complete value. Then ask whether the receipt describes requested execution or independently proves the executable resolved from PATH.
Run npm test and inspect the evidence contract. If you find a minimal counterexample, open an Issue or a focused PR directly; no maintainer pre-approval is needed. A clean-control result is useful too.