Repository navigation
spec(port): port the cover-traffic generation rate stability guard (Refs #8887) - #9814
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. |
This was referenced Oct 17, 2026
Merged
gHashTag
enabled auto-merge (squash)
October 17, 2026 18:18
…efs 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 a948f8a unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
force-pushed
the
port/cr-chat-07-i
branch
from
October 17, 2026 18:25
a948f8a to
42ee57f
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
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). Ninth CR-CHAT-07 ring target delivered: the rate-stability rules (R-CHAT-10) — batch ceiling (512), epoch floor (3), per-epoch rate floor (1) / ceiling (1000; boundary rate accepted in CGRS-10), strictly-increasing epochs, then the CV ceiling (0.3) over the whole batch — D5 verdict with every payload field (prev/current ride the verdict for NonMonotonicEpoch), original rule order, all ten CGRS tests transcribed plus a rule-order test (11 total, 0 vacuous). compute_cv (float mean + sqrt) does not lower — CV arrives caller-computed per the lane convention (#9698/#9747/#9811); structural rules fully in-spec; all fixture CVs Python-verified exact (unstable 1.4100, slight 0.0632, stable/boundary 0.0). t27b 11/11 native; t27c 11/11; 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.