Skip to content

test(ci): cover the three report modes; the loud operator reaches zero (#2492) - #2495

Merged
gHashTag merged 2 commits into
masterfrom
test/report-modes
Aug 23, 2026
Merged

gHashTag merged 2 commits into
masterfrom
test/report-modes

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

The last three loud survivors were report modes, each behind a flag CI never passes, and each file says so in its own words:

check_specs_parse.py     --all                  "a report, not a gate"
check_elab_ratchet.py    --allow-missing-tools  "reporting nothing, deliberately"
check_specs_generate.py  --summary              a counts table

The distinction between a report and a gate is worth keeping. Leaving the report's exit code unmeasured is not part of it — a report that prints its table and then reports failure breaks any script reading it.

The opt-out case is the sharpest

check_gate_preconditions proves the ratchet reds when its tools are missing. Nothing proved that --allow-missing-tools then returns success.

An opt-out that fails anyway is worse than none: it teaches that the flag does not work, and the next person removes the guard instead of passing it.

Where both operators now stand

survivors
--loud 0 across thirteen gates
silent 1 — the branch declared UNCOVERED with its reason

Two rows that are honest rather than clean

pack_index_consistency_gate.py and wp18_conformance_gate.py report no success path to break: they hold no bare return 0, every verdict being a ternary or a SystemExit. The loud operator takes only bare returns on purpose — forcing a ternary's whole line to 1 is the silent operator seen backwards and would be scored against the wrong control.

Those two are unmeasured in that direction, not covered, and the report says which.

The declaration that keeps matching

The one silent survivor's line has moved four times — :390, :403, :495, :516 — under other people's edits and mine, and the UNCOVERED note matched every time, because it names the branch by message.

Refs #2492

#2492)

Each sat behind a flag CI never passes, and each file says so in its own
words: --all is "a report, not a gate", --allow-missing-tools is
"reporting nothing, deliberately", --summary prints a counts table.

The distinction between a report and a gate is worth keeping. Leaving the
report's exit code unmeasured is not part of it: a report that prints its
table and then reports failure breaks any script reading it.

The opt-out case is the sharpest. check_gate_preconditions proves the
ratchet reds when its tools are missing; nothing proved that
--allow-missing-tools then returns SUCCESS. An opt-out that fails anyway
teaches that the flag does not work, and the next person removes the
guard instead of passing it.

Loud: zero survivors across thirteen gates. Two report "no success path
to break" -- pack_index_consistency_gate and wp18_conformance_gate hold
no bare `return 0`, every verdict being a ternary or a SystemExit. They
are UNMEASURED in this direction, not covered, and the report says which.

Silent: one survivor, the declared one. Its line has moved four times
now -- 390, 403, 495, 516 -- and the declaration matched every time,
because it names the branch by message.

Refs #2492
… none (#2492)

check_elab_ratchet offers --allow-missing-tools to accept a missing-tool
red locally. A sibling control proved the red; nothing proved the flag
then returns success, and the loud operator rewrote that return with
nothing noticing. An opt-out that fails anyway teaches that the flag does
not work, and the next person removes the guard instead of passing it.

Plus: a report is still a program with an exit code -- the report/gate
distinction is worth keeping and does not extend to leaving the exit
unmeasured.

And: "no path to break" is UNMEASURED, not clean. Two gates hold no bare
`return 0`; the loud operator skips ternaries on purpose, so those two
have no result in that direction and the report must say so. A row that
reads as a clean score when it is an absence of measurement is the
substitution this skill is about, and it is easiest to commit in your own
tool's output.

Refs #2492
@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 03:26:56 UTC

Summary

Status Count
Total Open PRs 6
PRs with Failing Checks 2
PRs with All Checks Green 4
READY 3
FAILING 2
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e905ba8eeb53 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 76e62ec into master Aug 23, 2026
27 of 29 checks passed
@gHashTag
gHashTag deleted the test/report-modes branch August 23, 2026 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant