You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Seals are stale on master: 126 gen-drift and 9 stale make coverage and spec-guards red #12972
Files: .trinity/seals/*.json only (the 135 seals listed by the failing coverage step of the Seal Coverage run on master 4cfd2f2, run 41172959376: 126 gen-drift, 9 stale). No spec, no compiler source, no workflow, no baseline file is edited. Out of scope: the cli-tri census, duplicate-bodies, "Documented t27c subcommands exist", emit-bitexact, Corpus ratchet.
User Scenarios
A contributor opens any PR against master and sees coverage ("Every seal still describes its spec") and spec-guards red for a reason the PR did not cause. They cannot tell their own breakage from the inherited one.
A reviewer wants to merge a docs-only PR; the required check is red because master's seals are behind the emitter (afea7d49d4, gen-rust slice-field capture) and behind five specs edited without a re-seal.
A maintainer reads docs/BRANCH-PROTECTION.md and expects the gate to be a signal, not noise.
Requirements
Re-save each listed seal with t27c seal <spec> --save, using a t27c whose compiler sources equal master. Re-sealing a gen-drift seal is a statement that the new output is the wanted one, so each gen-drift seal must change only gen_hash_rust (and sealed_at), which is what the emitter commit explains.
Run tri seals sync-twins so twin seals carry the newest claims.
A seal whose spec does not generate (the emit-bitexact specs) is not written with gen_hash=none; it is reported and left out of the commit.
No absolute home-directory path appears in any committed file.
One commit, Closes this issue, one PR against master.
Success Criteria
python3 tools/check_seal_coverage.py exits 0 on the PR head (the coverage check is green).
spec-guards is no longer red because of seals.
The diff touches only .trinity/seals/*.json.
A list of any seal left out, with the reason, is in the PR body.
Reopened: closed as spec-only. A specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.
Activity
seals: drop 23 baseline lines for gen-drift seals that now hold (Refs #…
seals: re-save 128 seal files for 70 specs (Refs #12972) (#12985)
chore(seals): re-save five of the six stale seals with a fresh t27c (…
Merge master 5550045 into the glass_window seal branch (Refs #12972)
fix(t27os): rename the LIVE MYCELIUM band qy so glass_window seals ag…
chore(seals): re-save fpga_fpga_wasm_board with a post-#12824 t27c (R…
chore(seals): re-save six gen-drift seals (config/migrate, runtime/ex…
chore(seals): re-seal t27os FrameGate, GlassWindow, QueenDash (Refs #…
ledgers: bless per the printed verdicts (Refs #12981, Refs #12959, Refs
wasm/doom: 23 of 23 named opcodes, the framebuffer link live, browser…
Merge master into claude/objective-tesla-774dea (Refs #12972)
specs(numeric,t27os): fix sha256 K table and micro5 oracle, restore t…
gHashTag commentedon Nov 17, 2026
Covered by specs/verified/seal_management.t27.
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M2 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.