master reds at 6939621f5: five stale seals after the t27b lane merge, ratchet ledger missing four rows #9072

After #9068 merged, master carries:

• 5 stale seals per spec-guards: queen_QueenGoldenChain.json, queen_QueenHolds.json, ci_DerivedData.json (stale already at bfb02df -- the spec(ci): which Boundary paths are derived records -- seals, the t27b ledger, FROZEN_HASH -- for gc_pair (Closes #9057) #9058 refresh bot left these three) and t27b_T27bStdmem.json, conformance_T27bConformanceStdmem.json (the lane's two: their seals were cut with a cc19d1f-era compiler, and 337b1d4's gen-rust changes moved the emitted bytes).
• t27b-native-ratchet red: the ledger blessed in t27b: std.mem.trim / indexOf / indexOfScalar / approxEqAbs + @sqrt comptime fold (Closes #8965, Closes #6488) #9068 came from a qemu-user sweep; the native run passes four more reference-passers (specs/queen/golden_chain.t27, specs/tri/t27b/ast_shape.t27, specs/tri/t27b/conformance/frame_address_caller_owned.t27, specs/tri/t27b/conformance/postfix_optional.t27) that the ledger does not name.

Fix: regen + reseal the five with the 6939621 compiler, re-bless the ledger from a native arm64 corpus run of the master tree. Same verified-on-lab flow as the lane.

🤖 Generated with Claude Code

User Scenarios

• Given the master branch at 6939621 with five stale seal files and a ratchet ledger missing four passing specs, when the seals are regenerated with the current compiler and the ledger is re-blessed from a native arm64 corpus run, then spec-guards report zero stale seals and t27b-native-ratchet passes with all four reference-passers present in the ledger.

Requirements

• FR-001: The five stale seals (queen_QueenGoldenChain.json, queen_QueenHolds.json, ci_DerivedData.json, t27b_T27bStdmem.json, conformance_T27bConformanceStdmem.json) MUST be regenerated and resealed using the compiler at 6939621.
• FR-002: The t27b-native-ratchet ledger MUST be re-blessed from a native arm64 corpus run of the master tree so that it includes the four reference-passers: specs/queen/golden_chain.t27, specs/tri/t27b/ast_shape.t27, specs/tri/t27b/conformance/frame_address_caller_owned.t27, specs/tri/t27b/conformance/postfix_optional.t27.
• FR-003: The regeneration and re-blessing MUST follow the same verified-on-lab flow used for the t27b lane merge.

Success Criteria

• spec-guards check exits 0 with zero stale seals reported for the five seal files.
• t27b-native-ratchet check exits 0 and the ledger contains exactly four additional rows matching the cited spec paths.
• All four cited spec files (specs/queen/golden_chain.t27, specs/tri/t27b/ast_shape.t27, specs/tri/t27b/conformance/frame_address_caller_owned.t27, specs/tri/t27b/conformance/postfix_optional.t27) appear in the re-blessed ledger.

Boundary

• specs/queen/golden_chain.t27
• specs/tri/t27b/ast_shape.t27
• specs/tri/t27b/conformance/frame_address_caller_owned.t27
• specs/tri/t27b/conformance/postfix_optional.t27
• specs/trinet/ledger.t27
• specs/tools/tri/seals.t27