Repository navigation
Description
spec-guards and coverage are red on every open pull request (#11583, #11634, #11635) from two stale seals on master itself, not from any diff, and nothing in the repository repairs them automatically: a grep -r reseal specs/crons/ specs/jobs/ returns nothing, so the repair has only ever been someone remembering to type it. Measured 2026-10-22 on a clean origin/master worktree (aeb772f46b):
tools/check_seal_currency.py --stale-specsreturns exactlyspecs/t27f/petal_menu.t27andspecs/t27os/bench.t27-- fourgen_hashfields stale on each of the two seals.tools/check_seal_coverage.pyreportsFAIL: 2 seal(s) newly do not hold:t27f_T27fPetalMenu.json [stale]andt27os_T27osBench.json [stale].- The seals were minted 2026-10-20 13:42; the specs moved after that in PRs T27 OS: bench.t27 -- boards, provenance of every number, project summary (Closes #11264) #11267 (bench, 20:42), T27 OS tools: registries, tri golden (own git), skills (Closes #11358) #11359 (both, 20:42), T27 OS: matte glass back, chat UX, home 20% smaller, white centre, petal A (Closes #11413) #11430 (petal_menu, 23:47) -- each landed past
spec-guardsbecause that workflow is deliberately not a required context (its own header; the standing issue for the class is Spec Guards has been red on master since #3435, and two PRs merged past it #3440). - Both specs' own tests pass today:
t27c test-reportgives 12/12 for petal_menu and 28/28 for bench, 0 vacuous. The reseal is therefore a statement that current compiler output is output we want, not a cover of a broken spec;t27c seal --saveenforces exactly this by refusing to write on a FAIL. - A baseline
t27c corpus --json(binary outcomes: generates and compiles per backend) is taken before the reseal and re-taken after; this issue's Success Criteria compare the two.
The repair is the gate's own remedy line, for these two specs only: t27c seal <spec> --save && tri seals sync-twins. Baselining (check_seal_coverage.py --update-baseline) is the WRONG repair here, by that tool's own wording: it records drift as accepted debt instead of recording what the compiler now produces.
Whether a steward job should reseal on a schedule is out of scope for this issue -- this issue makes the two gates green and records the measurement; the missing automation is a separate decision for the owner (it needs a cron card in specs/crons/ first, per the repo's cron registry rule).
Boundary
- .trinity/seals/t27f_T27fPetalMenu.json
- .trinity/seals/t27os_T27osBench.json
- tools/seal_baseline.txt
User Scenarios
Given a fresh clone of master, when both seal checks run with a built t27c, then check_seal_currency.py --stale-specs prints an empty list and check_seal_coverage.py exits 0.
Given the resealed tree, when t27c corpus --json is compared to the pre-reseal baseline taken on the same binary, then the acceptance columns (generates / compiles per backend) are identical -- a reseal changes only what seals claim, never what the compiler emits.
Given a pull request opened after this fix, when spec-guards and coverage run on it, then they no longer fail on petal_menu and bench, and any red they do report is about the PR's own change.
Requirements
- FR-001: The reseal MUST be produced by
t27c seal <spec> --savefor exactly the two stale specs, never by hand-editing a hash in.trinity/seals/. - FR-002:
tri seals sync-twinsMUST run after the reseal, so a twinned seal (if either spec carries one) inherits the same claims; it must refuse rather than propagategen_hash=none. - FR-003: The two specs' own tests MUST pass before the reseal is committed (measured: 12/12 and 28/28); a failing test makes the reseal the wrong move and this issue must be reopened with that fact.
- FR-004: The pre/post
t27c corpus --jsonacceptance columns MUST be identical; any moved column stops the repair and is reported here instead of being resealed past. - FR-005: No baseline line may be added to
tools/seal_baseline.txtfor these two specs (baselining is the explicitly wrong repair for gen-drift).
Success Criteria
python3 tools/check_seal_currency.py --stale-specsexits 0 with an empty list on the merged tree.python3 tools/check_seal_coverage.pyexits 0 on the merged tree (0 newly-unheld seals).git diff origin/master -- tools/seal_baseline.txtis empty.- The post-reseal
t27c corpus --jsonacceptance columns equal the pre-reseal baseline, and both JSON lines are attached to this issue. - On a PR opened after the merge,
spec-guardsandcoveragepass.
Activity
gHashTag commentedon Oct 25, 2026
One more instance, measured on PR #12060 at head
8dd35fbc4b(master merged in at15acb60995, 2026-10-25 10:49Z),spec-guardsjob:specs/storage/kv.t27last moved in #4660 (0bdd185d9f, "Wave 684"), which did not re-save the seal. No open PR re-seals it (gh pr list --search "StorageKv OR kv.t27 seal"is empty). The four seals of this morning (#12348) are green again;StorageKvis the one that keepsspec-guardsred on every PR that merges today's master.Fix is the usual one:
t27c seal specs/storage/kv.t27 --savefrom a master-tip build, thentri seals sync-twins, in one PR. Not done from the WASM lane: its localt27cpredates #12335 and would write the wrong hashes.gHashTag commentedon Oct 25, 2026
Follow-up to the StorageKv note above, 2026-10-25.
specs/storage/kv.t27without re-saving the seal, soStorageKv.jsonand its twin kept the 2026-10-20spec_hash. Not a compiler move.coveragejob ("Every seal still describes its spec",tools/check_seal_coverage.py) fails on it as well asspec-guards, on every open pull request.672aaca7d3(nobootstrap/commit between it and the tip), twins synced (497 consistent, 0 written). No spec change, no baseline edit. The spec's Zig road stays BLOCKED as the old seal already recorded.This issue stays open for the missing reseal automation.
seals: drop the stale FpgaHdmiGrab seal that #12430 re-added (Closes #…
numeric: drop the dead braceless invariant the parser discarded in zp…
policy: foreign exception for the AX7203 WASM board top (Refs #12456) (…
fpga(wasm): the 24 single-clock i32 ALU opcodes have one home -- alu_…
ci(fpga-build): synthesise the AX7203 WASM cell with a utilisation re…
fpga(wasm): P3-P7 of the AX7203 WASM cell to master: control flow, li…