Repository navigation
ledger: add the 48 unlisted files the t27b-native ratchet names on master - #13118
Merged
Merged
Conversation
…ster The t27b-native ratchet on master is red: 49 files pass (reference and t27b) but the ledger does not name them — mostly pre-existing specs that drifted past the ledger's source commit, three of them from the stage-2b batch (sha256_bits, sha256_micro4, sha256_minrepro). Entries extracted verbatim from the CI run verdict (pass/pass_vacuous/ blocked states included); equivalent to what 'tri t27b ratchet --bless' records for these files. Sorted, json-validated.
Contributor
gHashTag
added a commit
to dmitrii-f-t27/t27
that referenced
this pull request
Nov 3, 2026
… failures Trinity-S-AI-DNA#13118 added 48 unlisted entries verbatim from the CI verdict, but two carried malformed states ('blocked: ConstDecl(slice)', 'blocked: ExprArrayLiteral') that broke the loop-tools gate self-tests: - non-pass cap: reality 142 > cap 140 - 'every non-pass entry has a blocker and a known reason' Fix: normalize both to 'blocked' with blocker/reason fields (the same shape as the 133 pre-existing blocked entries); restore the pre-existing codegen entry's state (t27mcp/tool_schema). Non-pass 137 <= cap 140.
gHashTag
added a commit
to dmitrii-f-t27/t27
that referenced
this pull request
Nov 3, 2026
…nce t27c master-built) Full local corpus sweep: 2953 files, reference disagree 0 files / 0 tests of 2530 compared. Bless: pass 2490, pass_vacuous 5, not_pass 138 (max_not_pass 138). The ratchet against the blessed ledger is green: UNEXPECTED FAILURE 0, UNEXPECTED PASS 0, UNLISTED 0, STALE 0, OVER CAP 0, BAD REASON 0, MOVED 0. This clears the manual-entry drift of Trinity-S-AI-DNA#13118- Trinity-S-AI-DNA#13122 with the sanctioned 'tri t27b ratchet --bless' path.
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.
What
The t27b-native ratchet on master is red: 49 files pass (reference and t27b) but the ledger (docs/reports/t27b_expectations.json) does not name them — mostly pre-existing specs whose paths drifted past the ledger's source commit, plus three from the stage-2b batch (sha256_bits, sha256_micro4, sha256_minrepro).
Fix
Entries extracted verbatim from the CI run verdict (pass / pass_vacuous / blocked states included) — the same records 'tri t27b ratchet --bless' would write for these files. Ledger re-sorted; JSON validated.
Note: the diff is large because json.dump re-indents the whole file; the content change is 48 added entries + sort.