q147: class the new verifier in the Q63 census (wired-invoke, measured)
The verifier this item added is a committed verify_*.py at HEAD, so the Q65
gate faulted on it as UNCLASSED -- one new fault, 60 -> 61. The row is a
row-level add measured at de6d848 with q63_verify_scan.py --verbose, which
reads it 'ok 0 assert wired': CHECK invokes it by basename in its own
directory. Coverage 140 -> 141 of 191; the gate's fault count is back to 60,
unchanged from entry. The census is not re-taken whole here -- a whole re-take
would turn the 42 NEW-UNWIRED faults into tolerated rows.
This commit is contained in:
1 parent
de6d848fe6
commit
3118da3bd4
3 files changed
+15
-8
No files matched your search
@@ -76,6 +76,13 @@ wired-invoke wizard-work/ledger/verify_tree_census.py HEAD:wizard-work/ledger/ve
|
||||
gate-run wizard-work/ledger/verify_users.py q65:PASS
|
||||
wired-invoke wizard-work/ledger/verify_wizards.py HEAD:wizard-work/ledger/CHECK:4:python3 /root/troupe-standup/wizard-work/ledger/verify_wizard...
|
||||
gate-run wizard-work/ledger/verify_workflow.py q65:FAIL
|
||||
# row-level add (Q147, 2026-11-01): measured at de6d848 with q63_verify_scan.py
|
||||
# --verbose, which reads it `ok 0 assert wired`. The evidence is the invocation
|
||||
# line in wizard-work/ledger/workqueue-census/CHECK, in the same directory (the
|
||||
# bare-basename rule). Every other class row below and above is 13c217a's
|
||||
# reading, unchanged: the census is not re-taken whole here, because a whole
|
||||
# re-take would turn the 42 NEW-UNWIRED faults into tolerated rows.
|
||||
wired-invoke wizard-work/ledger/workqueue-census/verify_workqueue_census.py HEAD:wizard-work/ledger/workqueue-census/CHECK:39:python3 "$HERE/verify_workqueue_census.py" --selftest
|
||||
gate-run wizard-work/null/artifact-seal/verify_artifact_seal_oracle.py q65:PASS
|
||||
gate-run wizard-work/null/diffkit/verify_realrepo.py q65:PASS
|
||||
gate-run wizard-work/null/satkit-2026-10-26/verify_satkit.py q65:PASS
|
||||
|
||||
|
Can't render this file because it contains an unexpected character in line 45 and column 92.
|
Reference in new issue
Block a user