Repository navigation
spec(port): port the cover-traffic replay detection guard (Refs #8887) - #9823
Merged
1 commit merged intoOct 17, 2026
Merged
1 commit merged into
1 commit merged into
Conversation
…Tag#8887) The fifteenth CR-CHAT-07 ring target (W2, R-CHAT-10): the replay rules - the batch ceiling, then per window the zero-index probe, the zero-hash probe, the emission floor (ten; the exact boundary passes), the strictly-increasing index and the repeated-hash scan - as the D5 verdict with every payload field, the original's rule order, and all ten CTRD tests transcribed plus helper and rule-order tests. The BTreeSet dedup becomes a scan over the windows already visited; the hashes stay the fixed [32]u8 form. 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;
Contributor
Author
|
Merge request for the gHashTag merger: steward READY (required all SUCCESS — validate, check-linked-issue, parse-ratchet, t27b-native-linux, t27b-native-macos; the red ones are non-required per Q16 and red on master too). Ledger row included; one-line rebase if the earlier lane PRs land first — I take it on request. |
gHashTag
enabled auto-merge (squash)
October 17, 2026 18:12
gHashTag
disabled auto-merge
October 17, 2026 18:41
gHashTag
closed this pull request by merging all changes
into
gHashTag:master
in
12f5af8
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 #8887 (CR-CHAT-07 ring tracker). Parent epic: gHashTag/trios#1812 (W2, own lane, T-PORT). Fifteenth CR-CHAT-07 ring target delivered: the replay rules (R-CHAT-10) — batch ceiling (256), per-window zero-index probe, zero-hash probe ([32]u8), emission floor (10; exact boundary passes in CTRD-10), strictly-increasing indexes, repeated-hash scan — D5 verdict with every payload field (prev/current ride the verdict for NotIncreasing), original rule order, all ten CTRD tests transcribed plus helper and rule-order tests (12 total, 0 vacuous). BTreeSet → visited-scan; hashes stay the fixed [32]u8 form. t27b 12/12 native; t27c 12/12; gen-rust compiles under rustc (0 errors, 0 &'static str, 0 Vec<const); coverage Untested 0; seal all hashes MATCH; ledger row included (pass, non-pass untouched). Dedup checked. Sequencing: one-line ledger rebase if the earlier lane PRs land first — I take it on request.