Repository navigation
ci(seals): re-stamp the two tuple seals master left stale (Refs #11912 #11840) - #11939
Merged
Merged
Conversation
…#11840) #11930 rendered parameterised const structs as Zig generic fns but missed tuple.t27 in its seal re-stamp sweep: the audit grep used [A-Za-z_]+ for the declaration name, and `Tuple2`/`Tuple3` carry a digit, so `pub const Tuple2(A, B) = struct {` never matched. Master inherited two stale seals (TriTuple.json, collections_TriTuple.json; gen_hash_zig f49f77e5 -> a87c06f1). Re-stamped with `t27c seal --save specs/tri/collections/tuple.t27`. check_seal_currency: STALE generated-code hash 2 -> 0, exit 0. Tuple2/Tuple3 now emit `pub fn Tuple2(comptime A: type, comptime B: type) type { return struct { first: A, second: B, }; }` (verified: fields carry A/B inside the generic fn); the module's own remaining BLOCK is the fn-level generic layer (`fn pair(a: A, b: B)`), the slice #11930 filed as follow-up -- not this seal repair.
gHashTag
enabled auto-merge
October 24, 2026 01:49
Contributor
This was referenced Oct 24, 2026
Closed
chore(seals): shrink the stale-hold ledger -- two ledgered-stale seals now hold (Refs #11038)
#11963
Merged
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
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
#11930 rendered parameterised const structs as Zig generic fns but missed
tuple.t27in its seal re-stamp sweep: the audit grep used[A-Za-z_]+for the declaration name, andTuple2/Tuple3carry a digit, sopub const Tuple2(A, B) = struct {never matched. Master inherited two stale seals:.trinity/seals/TriTuple.json.trinity/seals/collections_TriTuple.json(
gen_hash_zigf49f77e5 -> a87c06f1)Fix
Re-stamped with
t27c seal --save specs/tri/collections/tuple.t27.tools/check_seal_currency.py: STALE generated-code hash 2 -> 0, exit 0.The grep defect is recorded: a character class that rejects digits in declaration names silently narrows an audit's corpus. Tuple2/Tuple3 themselves emit correctly since #11930 --
pub fn Tuple2(comptime A: type, comptime B: type) type { return struct { first: A, second: B, }; }; the module's remaining BLOCK is the fn-level generic layer (fn pair(a: A, b: B)), the slice #11930 filed as follow-up.Also observed on master (not this PR's scope)
signed_receipt_reader(2 tests) andgen_python_hello_world_parses_and_importsfail at 58ad4fa, at 72a5c0d and at the current tip alike -- pre-existing master reds in the mega-epic(t27f): every T27F and gen-UI track in one map -- visual spec core, tools, Live, reels, factories, TRI CLAW #11038 repair series, not introduced by fix(gen-zig): render parameterised const structs as Zig generic fns (Refs #11912 #11840) #11930.queen_QueenWorktreeKeep,t27b_T27bWasm) now HOLD for their generated code; the ledger can shrink viatools/check_seal_coverage.py --update-baseline.