feat(t27b): bless accounts for a cap rise; doctor alarms from per-spec records - #6242
Merged
Merged
Conversation
…c records steward.t27 gains cap_rise_is_new and is_alarm (62 tests, both compilers). `tri t27b ratchet --bless` prints the accounting on a refused rise and `--accept-new` raises the cap by exactly the specs new to the ledger; a rise from a named spec is still refused. The doctor's LAB-ERROR counts fail/timeout through is_alarm, so a fail the reference shares (build_verify.t27) is no longer an alarm. Closes #6237 Refs #6063 #6198 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 4, 2026
Contributor
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #6237
Refs #6063 #6198
Slice 5 of moving the t27b steward into
.t27. Two decisions move intospecs/tri/t27b/steward.t27:cap_rise_is_new(not_pass, old_cap, new_not_pass): a cap rise is covered only if the non-pass entries the old ledger already named still fit the old cap.is_alarm(t27b, reference): a mismatch or a crash is always an alarm; a fail or a timeout is an alarm only where the reference passes.Tool
tri t27b ratchet --blessprints the accounting when it refuses a rise, and says whether--accept-newwould cover it.--accept-newraises the cap by exactly the number of new specs. A rise from a spec the ledger already named is still refused.resultsthroughis_alarm. When a run has no per-spec results, it falls back to the summary.Evidence
t27b test --check: 62/62. t27c labtest-report: 62/62.gen/c/tri/t27b/steward.cregenerated on the t27c lab.tri t27b gen-checkanswersSAME b46d92e084be.--accept-new, refused with594 non-pass now = 553 already named + 41 new to the ledger.--accept-new, the cap becomes 594, the same number chore(t27b): re-bless the expectations ledger from lab run 88862a949 #6235 set by hand.LAB-ERROR t27b_fail 1false alarm forbuild_verify.t27is gone. The reference fails that spec too.🤖 Generated with Claude Code