Repository navigation
ledger: drop specs/nn/hslm.t27, now parsed with no discard (Closes #10071) - #10078
Merged
Merged
Conversation
…0071) #10055 made specs/nn/hslm.t27 parse with no discarded tokens, so the corpus ratchet on master reports it as an UNEXPECTED PASS (and as a DISCARD WORSENED with no reading). The pin is dropped and max_entries follows the count down, 82 -> 81. The entries match the ledger's own bless command, run on the Railway lab, byte for byte; the bless serializer would also drop the hand-written _why_entries_fell/_why_entries_rose fields, so they are kept and the diff is the one entry plus the cap line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
gHashTag
enabled auto-merge (squash)
October 17, 2026 18:45
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 #10071
What
Master fails the corpus ratchet, and every open PR inherits the red check. #10055 made
specs/nn/hslm.t27parse with no discarded tokens, but the expected-failure ledger still pinned it asparse-no-discard(153 tokens, issue 1959). CI run 39055607561 on master:This PR drops that one entry and lowers
max_entries82 -> 81. The diff is one entry removed and one cap line changed, nothing else.How it was produced
t27c suite --repo-root . --ratchet --corpus-only --bless-expectationson the Railway lab (master a18d7ee) blessed 81 entries with cap 81, RATCHET: CLEAN, exit 0, and its diff was exactly this entry plus the cap. The bless serializer also drops the hand-written top-level fields_why_entries_felland_why_entries_rose, so the committed file is the same edit with those two fields kept. The 81 entries are byte-identical to the bless output.Verification
On the Railway lab, master a0fc4e3 with this file applied, no bless:
The other two master reds
specs/tri/t27b/emit_kit.t27). Nothing to do here.cli/tri/src/gates.rs:9012still hasinclude_str!on the deleted.github/workflows/brain-seal-refresh.yml, in the testthe_motivating_workflow_records_its_own_reason. The fix is deleting that test (or pointing it at a workflow that exists), which is an edit to existing Rust and needs the owner'sowner-approved-foreignlabel. It is tracked by cli-tri: retire deleted-workflow test and refresh measured census pins #9634 and left for the owner there; this PR does not touch Rust.🤖 Generated with Claude Code