Repository navigation
spec(port): port the cover-traffic payload length distribution guard (Refs #8887) - #9820
Closed
dmitrii-f-t27 wants to merge 1 commit into
Closed
dmitrii-f-t27 wants to merge 1 commit into
dmitrii-f-t27 wants to merge 1 commit into
Conversation
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
…(Refs gHashTag#8887) Rebuilt as one commit on master a1002be so it merges; docs/reports/t27b_expectations.json rows from both sides kept (union, sorted). Content is otherwise the PR head a7a4da4 unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
force-pushed
the
port/cr-chat-07-m
branch
from
October 17, 2026 18:27
a7a4da4 to
0282b32
Compare
gHashTag
disabled auto-merge
October 17, 2026 18:41
Owner
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.
Refs #8887 (CR-CHAT-07 ring tracker). Parent epic: gHashTag/trios#1812 (W2, own lane, T-PORT). Thirteenth CR-CHAT-07 ring target delivered: the length-distribution rules (R-CHAT-10) — batch ceiling (128), per-batch repeated-id scan ([8]u8), class floor (2) / ceiling (16), observation floor (10), chi-squared ceiling (50.0; exact boundary passes in CTPL-09, the rule strictly greater) — D5 verdict with every payload field, original rule order, all ten CTPL tests transcribed plus helper and rule-order tests (12 total, 0 vacuous). The chi-squared statistic arrives in the record exactly as the original carries it (caller-computed over the histograms — the record's own field); BTreeSet → visited-scan. 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.