Repository navigation
Conversation
) The thirty-first W2 target of the CR-CHAT-04 ring tracker: the key-uniqueness rules - the batch ceiling, then per derivation the empty-label probe, the key-length check, the zero-key probe, the strictly-increasing index and the repeated-key scan - as the D5 verdict with every payload field, the original's rule order, and all ten PKDU tests transcribed plus helper and rule-order tests. The original's Vec<u8> key becomes the fixed [32]u8 form plus its length, the String label becomes its length - the only property any rule reads. The BTreeSet dedup becomes a scan over the visited derivations; the boundary fixture's little-endian index bytes come out of the identity byte table, no narrowing anywhere. Checks (conventions 0-14): t27b test 12 passed 0 failed; t27c test-report 12/12, 0 vacuous; gen-rust output compiles under rustc; coverage Untested 0; ASCII only; seal saved, all hashes MATCH;
…ave2-ad # Conflicts: # docs/reports/t27b_expectations.json
… import (Refs #8884) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
enabled auto-merge
October 18, 2026 02:54
Owner
Author
Contributor
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
2 participants
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.
Refs #8884 (CR-CHAT-04 ring tracker)
This PR lands #9755, the padding key derivation uniqueness guard. #9755 was fully green, but its branch lives in a fork that maintainers cannot push to, so it lands from here: the original commits are kept as they were, with two commits added on top.
On top of #9755
keys_equalwas a byte-for-byte copy ofids32_equalinspecs/port/trios/crates/trios-chat/common/helpers.t27, which spec(port): share the duplicated CR-CHAT helpers blessed by #10098 (Closes #10159) #10161 made the one home for the CR-CHAT helpers. Once master was merged in,duplicate-bodiesflagged it. The spec now hasuse port::trios::crates::trios-chat::common::helpers;and callsids32_equal. Its seal is re-saved.Evidence (Railway lab)
seal --verify: all hashes MATCH.dupe_scan:ids32_equalis no longer flagged. The remainingfind/hasgroups are master's and are fixed by fix(ci): master green again -- stale corpus-ledger rows, census re-pin, t27mcp duplicate helpers (Closes #10171) #10172.t27b buildstops atExprArrayLiteral(reference empty typed)(line 216). That is the blocker spec(port): port the padding key derivation uniqueness guard (Refs #8884) #9755'st27b_expectations.jsonrow already records.🤖 Generated with Claude Code