Repository navigation
chore(claw): reseal 19 seals with stale dependency hashes - #10729
Merged
Merged
Conversation
gHashTag
enabled auto-merge (squash)
October 19, 2026 00:15
Contributor
This was referenced Oct 19, 2026
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.
What
This PR reseals the 19 TRI CLAW seals whose recorded dependency hashes no longer matched their dependencies on master. It changes seal data only; no spec changes.
Each seal now records the current hash of each spec it imports. Before this change, 23 recorded dependency hashes in these 19 seals were stale. Most were from #10714, which changed
specs/claw/text.t27without resealing its importers. They still passedseal --verifybecause the verifier never reads dependency hashes (#10727).The other two stale claw seals,
claw_ClawCheckStateandclaw_ClawMergeLane, are resealed in #10726, so this PR leaves them alone.What changed in the JSON
spec_hashsealed_attest_runnerbuilt_by(t27c-bootstrap@0.5.2+4ab200073->+9448ab4be)test_runnerandbuilt_bychanged because the lab's t27c is a newer master build than the one that wrote those four seals. No spec hash and nogen_hash_*changed.Verification (Railway lab, clean detached worktree at 5440d35)
seal <spec> --verifybefore resealing: all 19 matched, so every seal was valid against its own spec and generated code; only the dependency block was stale.seal <spec> --savewith zig on PATH, no--force: no failures.seal --verifyoverspecs/claw/*.t27plusspecs/verified/gen_file_check.t27: 32 of 32.shasum -a 256of each recorded dependency against the branch): no stale entry in the 19 resealed files. Only CheckState and MergeLane still record the oldtext.t27hash, and test(claw): kill the real check_state.t27 and merge_lane.t27 mutation survivors #10726 fixes those.Self-check
seal --verifychecks dependencies (seal --verify never checks dependency hashes; 21 claw seals record stale ones #10727, a Rust change that needs the owner's label), the next spec edit that skips resealing its importers will make these seals stale again.Refs #10727.
🤖 Generated with Claude Code