Repository navigation
seals: re-seal the four gen-drifted t27os specs (Closes #13151) - #13152
Merged
Merged
Conversation
An emitter fix changed generated output without re-sealing, so four seals (glass_window, hot_reload, pty_sys, release) described output the compiler no longer produces and every open PR failed coverage and spec-guards with their names. Re-sealed from the master-built t27c at 1bc28b4. release.rs also regenerated with git add -f per #11328: it missed F_LIVE_DEV the current generator emits. No baseline entries.
Contributor
This was referenced Nov 2, 2026
Merged
added 2 commits
November 3, 2026 13:08
…end for gen-extern (Closes #13151) #13150 moved the gen-drift attach to NOTED.append and added a new kind gen-extern, but _check_legend still read only bad.append sites -- so on any tree the negative control either called gen-drift unreachable or named gen-extern missing its legend (W721's own law). Both append sites count now, and gen-extern has its line. Self-check: legend covers 10 of 10 kinds; end-to-end controls green.
…extern (Closes #13151) #13150 notes gen-drift instead of failing it (#13117), and added the gen-extern kind without a legend line, so _check_legend failed on any tree: it read only bad.append sites and the new kind had no reader line. Both append sites count now, gen-extern has its legend, and the W721 history narration moves to the issues. Self-check: 10 of 10.
Collaborator
Author
|
Division of labor noted: the checker legend fix landed in two independent variants (c2a4bb4, c9aae2d). The branch is DIRTY against a moved master -- whoever drives the lane next resolves the conflict; the content (4 re-seals + regenerated release.rs + checker legend fix) is agreed on all sides. #13151 stays the traceability anchor. |
Collaborator
Author
|
Conflict resolution data point: master moved but its own Seal Coverage is still red (latest master run failure, 2026-11-02T21:03Z) -- master-side versions of the three conflicting seal files (glass_window, hot_reload, pty_sys) do NOT hold. Keep OUR side for those three (verified all hashes MATCH against the master-built t27c here); the conflict is master carrying someone else's host-hostile re-seal, cf. #13117. |
Master's own versions of these seals do not hold (master Seal Coverage red, run of 2026-11-02T21:03Z); ours verify all hashes MATCH against the master-built t27c. Resolution data recorded on PR #13152.
Contributor
PR DashboardGenerated at: 2026-11-03 06:31:31 UTC
Summary
Seal Status
|
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.
Four seals drifted on master after an emitter fix (names and run ids in #13151). Repaired per FR-001/FR-002: re-sealed from the master-built t27c at 1bc28b4; release.rs regenerated with git add -f per the #11324->#11328 lesson (it missed F_LIVE_DEV the current generator emits). No baseline entries. Local on this head: seal coverage OK; all four seals verify all MATCH.