Recordsnpmdevtools-protocolfailure issue
Failure signature
PROJECT_TEST ENOENT Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-18 · Last seen: 2026-08-18
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 0.0.1686980 not measured
- 0.0.1684464 not measured
- 0.0.1413902 PASS 3 passing observations
- 0.0.1367902 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-18 → 2026-08-18
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 0.0.1367902 → first passing release 0.0.1413902
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_TEST: 2
- No resolved dependency tree for 0.0.1413902 or for 0.0.1367902, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.