Skip to content

fix(seals): re-seal runtime/process and kanban-card-chat (Closes #6256) - #6257

Open
gHashTag wants to merge 1 commit into
masterfrom
claude/t27c-reseal-master
Open

gHashTag wants to merge 1 commit into
masterfrom
claude/t27c-reseal-master

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Closes #6256. Refs #6092

Master has been red on the t27c lab's seal-currency and seal-coverage since ea6839b (run of 77e5c44c5). The cause is three stale seals, left open by #6221 (its section 4):

seal spec changed by
runtime-process.json and twin runtime_runtime-process.json specs/runtime/process.t27 3d73d51
automation_automation::kanban_card_chat.json specs/automation/kanban-card-chat.t27 9a5b7f5 (#5680)

What I did: re-sealed both specs on the Railway lab, in a worktree of 77e5c44, with the lab's t27c built from that commit and zig 0.16.0: t27c seal <spec> --save && tri seals sync-twins. Nothing was built on the workstation. Only the three seal files changed. Every new gen_hash_* equals the "current" value that the lab's seal-currency log printed for that seal.

Pre-existing, not changed here: specs/runtime/process.t27's seal still records tests.blocked, because the generated Zig does not compile (spec.zig:96:38: expected '}', found ']'). That was already in the old seal; only the temp path in the message changed.

Verdict: the lab watches claude/t27c-*. Its run of this head decides whether this is green.

🤖 Generated with Claude Code

Both specs changed after sealing (3d73d51, 9a5b7f5), so master has
been red on seal-currency and seal-coverage since ea6839b. Re-sealed on
the Railway lab with the t27c built from 77e5c44 and zig 0.16.0; the
new gen hashes are the "current" values the lab's seal-currency log
printed. Only seal files change.

Closes #6256

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

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-04 20:21:18 UTC

Summary

Status Count
Total Open PRs 47
PRs with Failing Checks 33
PRs with All Checks Green 14
READY 12
FAILING 33
PENDING 0
NO CHECKS YET 0

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

Seal Status

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

This branch has not been deployed

No deployments
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.

Re-seal runtime/process and kanban-card-chat: master red on seal-currency since ea6839b2c

1 participant