Skip to content

ledger: add the 48 unlisted files the t27b-native ratchet names on master - #13118

Merged
gHashTag merged 1 commit into
masterfrom
fix/sha256-ledger
Nov 2, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/sha256-ledger

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator

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.

…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.
@gHashTag
gHashTag merged commit e153734 into master Nov 2, 2026
30 of 35 checks passed
@gHashTag
gHashTag deleted the fix/sha256-ledger branch November 2, 2026 12:04
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-02 12:07:51 UTC

Summary

Status Count
Total Open PRs 46
PRs with Failing Checks 43
PRs with All Checks Green 3
READY 2
FAILING 43
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 43 + 0 + 0 = 45, and there are 46 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e75b498e5e79 != 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 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.
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