Skip to content

seal: re-save the seven stale seals after the stage-2b merge batch - #13112

Merged
gHashTag merged 1 commit into
masterfrom
fix/stale-seals
Nov 2, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/stale-seals

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator

What

Seal Coverage on master lists 8 stale seals — the stage-2b merge changed specs without re-saving their seals (WindowKeep was fixed in #13111; these are the remaining 7).

Fix

Re-saved from the master-built t27c: clade_improve, HotReload, Install, Release (direct re-save); GlassWindow, PlistMain, PtySys (--force: @extern specs, which t27c cannot compile by design — they are tested with t27b per CLAUDE.md; the seal records the t27b-verified state).

Verification

No home paths embedded (secret-scan clean).

Seal Coverage on master lists 8 stale seals (spec changed after sealing):
clade_improve, GlassWindow, HotReload, Install, PlistMain, PtySys,
Release, WindowKeep (WindowKeep fixed in #13111).

Re-saved from the master-built t27c. GlassWindow/PlistMain/PtySys need
--force: they are @extern specs, which t27c cannot compile by design
(tested with t27b per CLAUDE.md); their seals record the t27b-verified
state. No home paths embedded (scan-clean).
@gHashTag
gHashTag merged commit be7934f into master Nov 2, 2026
26 of 31 checks passed
@gHashTag
gHashTag deleted the fix/stale-seals branch November 2, 2026 11:21
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-02 11:23:31 UTC

Summary

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

These columns do not partition: 2 + 42 + 0 + 0 = 44, and there are 45 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
…r t27c

The previous reseal (Trinity-S-AI-DNA#13112) used a stale t27c (t27-build at 05b6448,
an old master) whose gen output differs from CI's for zig/verilog:
4 gen_hash mismatches kept Spec Guards red.

Rebuilt t27c at master be7934 and re-saved the four seals. GlassWindow
and PtySys remain --force (@extern specs, t27c cannot compile them by
design; seals record the t27b-verified state).
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