Repository navigation
t27b ledger: bless 263 unlisted specs from the native master run (Closes #10195) - #10196
Merged
Merged
Conversation
#10195) Re-blessed docs/reports/t27b_expectations.json with `tri t27b ratchet --bless --accept-new` on the Railway lab, from the t27b-native-run artifact of master run 39094812421 (commit fdeb1db). Counts that moved: - entries appended: 263 (217 pass, 3 pass_vacuous, 43 blocked) - pass 1495 -> 1712 plus pass_vacuous 0 -> 3 (ledger now counts 1712/3) - max_not_pass 33 -> 76 (33 already named + 43 new, accounted by the tool) - header source: a9ad525 -> fdeb1db Counts that did not move: UNEXPECTED FAILURE 0, UNEXPECTED PASS 0, STALE 0, MOVED 0, BAD REASON 0, OVER CAP 0. No existing row changed. The ratchet against the new ledger is green with UNLISTED 0. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 18, 2026 04:02
Contributor
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
1 participant
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 #10195
What
Re-blesses
docs/reports/t27b_expectations.jsonsot27b-native-ratchetgoes green on master. The file is tool-written:tri t27b ratchet --bless --accept-newon the Railway lab, from thet27b-native-runartifact (run.json, sha256 ce55ce92...) of master run 39094812421 (commit fdeb1db, native arm64). The regenerated ledger was pulled back with tar|base64 and its sha256 (9c38486c...) matches the lab's copy. No row was edited by hand.Counts that moved
max_not_passThe cap rise is exactly the 43 non-pass specs new to the ledger (33 already named + 43 new, 0 named non-pass entries left the run); the tool refuses a rise that its accounting does not cover and only allowed it with
--accept-new. The 43 new blocked rows carry the reasonunimplementedand the first construct t27b rejects (for exampleExprCall(undeclared fn),ConstDecl,ExprReturn(frame address)).Counts that did not move
UNEXPECTED FAILURE 0, UNEXPECTED PASS 0, STALE 0, MOVED 0, BAD REASON 0, OVER CAP 0, UNJUDGED 0, VACUITY MEASURED 0. No existing row changed; the diff appends 263 rows and edits three header lines.
Check
Against the new ledger the same run prints
tri t27b ratchet: green -- run fdeb1db16 vs ledger fdeb1db16: ... UNLISTED 0 ....🤖 Generated with Claude Code