From 4c9db4321dc475e4e668f76dc7f940ba66b172d5 Mon Sep 17 00:00:00 2001 From: volt Date: Sun, 1 Nov 2026 02:29:16 +0000 Subject: [PATCH] volt: q143 baseline takes its own row, and the report states the load limit it measured --- wizard-work/volt/q143-check-sweep/REPORT.md | 18 ++++++++++++++++++ .../q143-check-sweep/check_entry_baseline.tsv | 1 + 2 files changed, 19 insertions(+) diff --git a/wizard-work/volt/q143-check-sweep/REPORT.md b/wizard-work/volt/q143-check-sweep/REPORT.md index d35de9f..12f92eb 100644 --- a/wizard-work/volt/q143-check-sweep/REPORT.md +++ b/wizard-work/volt/q143-check-sweep/REPORT.md @@ -80,6 +80,24 @@ SET against the baseline, ~0.2 s, no execution), `sweep` (the full grade). * That a green entry point measures the right thing -- that is the tool's own `--selftest`, and this instrument cannot see it. * That the rc-124 rows are slow rather than hung -- only a longer timeout settles it. +## (5) The limit this reading has, measured on itself + +A second `--check` at `--jobs 12` (against `--jobs 8` for the take) moved four +rows that read green in the baseline into **rc 124** -- `wizard-work/volt/CHECK-q110`, +`CHECK-q126`, `CHECK-q97` (0 -> 124) and `CHECK-q118` (1 -> 124) -- because the +machine was carrying twelve concurrent entry points plus this tick's own +subprocesses. So the code a slow entry point reports is a function of the load it +ran under, not only of the artifact, and the baseline is a reading at `--jobs 8` +on an idle host. The honest use of this instrument is a re-take on an idle host +before believing a REVERT line; the 124s are flagged rather than hidden, which is +what keeps that limitation visible. + +Its own row is the other limit: `CHECK-q143` reads **rc 1** while its own row is +absent from the baseline (its `paths` leg faults on exactly the unreviewed-entry +class it grades), so the row is recorded at the rc it actually printed, with the +reason. With the row present, `--paths` reads 98 entry points / 98 baseline rows / +0 faults (measured). + * That `CHECK-q143` is wired into `tools/verify.py` -- it is not, this tick; the `paths` leg is 0.2 s and is the obvious thirteenth leg, and wiring it means moving the gate's own selftest cell counts, which this tick did not do. diff --git a/wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv b/wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv index 64ede3a..da05bf5 100644 --- a/wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv +++ b/wizard-work/volt/q143-check-sweep/check_entry_baseline.tsv @@ -98,3 +98,4 @@ wizard-work/volt/CHECK-q97 0 Q97 GATE: rc 0 -- a refusal that echoes the invocat wizard-work/volt/CHECK-toolsmd-drift 124 TIMEOUT after 45s wizard-work/volt/q137-open-set/CHECK-q137 0 q137: 4 leg(s), all passed wizard-work/volt/q140/CHECK-q140 0 Q140 OK +CHECK-q143 1 self-referential: its own row absent while this baseline was taken; legs 1-2 green (selftest 20/20)