Skip to content

seals(t27os): re-save three stale seals left by #13335 (Refs #13335) - #13343

Closed
gHashTag wants to merge 1 commit into
masterfrom
claude/reseal-t27os-13335
Closed

gHashTag wants to merge 1 commit into
masterfrom
claude/reseal-t27os-13335

Conversation

@gHashTag

@gHashTag gHashTag commented Nov 8, 2026 •

Copy link
Copy Markdown
Collaborator

Refs #13335

What

PR #13335 edited three t27os specs without re-saving their seals, so master Spec Guards (seal-currency step) reports STALE generated-code hash : 3 since 85e0a7c (run 42446456796 at cf42110). This PR re-saves exactly those three seals; no spec or other file changes.

Seal Spec Tests
t27os_KeysyncScopeProbe.json specs/t27os/keysync_scope_probe.t27 2/2 (was 1/1 vacuous)
t27os_T27osHdmiGrabMain.json specs/t27os/hdmi_grab_main.t27 3/3
t27os_T27osHiveFeedAcceptance.json specs/t27os/hive_feed_acceptance.t27 10/10

All 12 new gen hashes (rust, zig, c, verilog per seal) equal the current= prefixes in the master run log. No twin seals reference these specs; no /Users path in the diff.

How

Re-saved with seal --save in a T27 OS shell-cell pane, compiler t27c-bootstrap@0.5.2+2cf81c119 (#13290 head). bootstrap/ on master differs from that commit only in generated header comments.

Unblocks the inherited spec-guards red on #13233.

Inherited red (not this PR)

coverage (Every seal still describes its spec) is red on master 1959e43 too (run 42449157784, 5 seals). This PR clears the three t27os [stale] entries; the two left are numeric_Sha256.json and numeric_Sha256Micro5.json [tests-fail] (the specs' own tests fail on master, after ccef616 / #13336), unrelated to these seals.

🤖 Generated with Claude Code

PR #13335 edited specs/t27os/keysync_scope_probe.t27, hdmi_grab_main.t27
and hive_feed_acceptance.t27 without re-saving their seals, so master
Spec Guards (seal-currency) reports STALE generated-code hash : 3, all
four backend hashes stale in each (run 42446456796 at cf42110).

Re-saved in a T27 OS shell-cell pane with the bootstrap compiler built
from #13290 head 2cf81c1 (bootstrap/src identical to master; only
generated header comments differ). Only the three seal files change.

Refs #13335

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-11-08 05:12:04 UTC

Summary

Status Count
Total Open PRs 48
PRs with Failing Checks 44
PRs with All Checks Green 4
READY 3
FAILING 44
PENDING 0
NO CHECKS YET 0

These columns do not partition: 3 + 44 + 0 + 0 = 47, and there are 48 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b882be1e4933 != 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

gHashTag commented Nov 8, 2026

Copy link
Copy Markdown
Collaborator Author

Superseded by #13344: it restores the three t27os specs (drops the #13335 placeholder tests), so the master seals describe them again, and it also fixes the sha256 tests-fail. Merging this PR on top would leave these three seals stale against the restored specs. Reopen if #13344 is abandoned.

@gHashTag gHashTag closed this Nov 8, 2026
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