Repository navigation
seals: reseal the four fpga/board specs #10014 edited (Closes #10052) - #10053
Merged
Merged
Conversation
#10014 changed specs/boards/xc7a100t_minimal.t27, specs/boards/wukong_v1.t27, specs/fpga/placement.t27 and specs/fpga/stdlib.t27 without resealing, so check_seal_currency reported 8 STALE seals and Spec Guards and Seal Coverage went red for every PR. Written by `t27c seal <spec> --save && tri seals sync-twins` on the Railway lab at d03afb0. No --update-baseline. Lab: STALE generated-code hash 0, check_seal_coverage OK. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
gHashTag
enabled auto-merge (squash)
October 17, 2026 17:39
Owner
Author
|
Two checks fail on this PR. Neither comes from its diff, which holds only 8 seal JSON files:
Once this PR merges, Spec Guards and Seal Coverage should go green on master. |
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 #10052
What
#10014 (2f39502) edited four specs without resealing them, so Spec Guards and Seal Coverage went red on master and
on every open PR:
The diff holds only these 8 tool-written
.trinity/seals/*.jsonfiles. No spec, no code, and no baseline entry.How
On the Railway lab, in a fresh clone of master at d03afb0, with t27c and tri built from that tree:
--update-baselinewas not used. The check says baselining gen-drift is the wrong repair.Evidence (lab)
Test counts in the new seals: Placement 14/14, Stdlib 17/17, BoardMinimalXC7A100T 23/23, BoardWukongV1 15/15,
all with 0 failed and 0 vacuous.
Not fixed here
cli-tri is also red on master:
cli/tri/src/gates.rs:9012usesinclude_str!on.github/workflows/brain-seal-refresh.yml, which #9117 deleted. Fixing it means editing Rust, which needsowner-approved-foreign; see #10052.🤖 Generated with Claude Code