Repository navigation
evidence(OMN-13196): rebind infra receipt to narrowed PR #2007 head f432045df - #2692
Conversation
|
Warning Review limit reached
More reviews will be available in 2 hours, 26 minutes, and 8 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…2045df Supersedes the merged #2686 evidence after the omnibase_infra impl PR #2007 was rescoped to benchmark-only (the two src docstring edits, pure doc comments, moved to B5/OMN-13204 to keep the PR out of the deploy-gate runtime-path matcher). The force-push moved PR #2007's head 57f66e31f -> f432045df. Dual-key binding for BOTH impl PRs, now keyed to this OCC PR (#2692): - pr-omnibase_core: commit_sha a77ef5ecb (PR #1250) + pr_number 2692 - pr-omnibase_infra: commit_sha f432045df (PR #2007) + pr_number 2692 - contract check_value greps each receipt for status PASS + pr_number 2692 + the impl commit_sha; both contract_sha256 rebound to the yamlfmt-normalized contract. verifier=receipt-gate-local (!= runner omn-13196-impl). Honesty + hardening pass. OMN-13196
85295ec to
0be35b0
Compare
OMN-13196 — rebind infra receipt to narrowed PR #2007 head
Evidence-Source: a77ef5ecb2e7bb7b7f6761fb7468f5741e9cde23
Evidence-Ticket: OMN-13196
Follow-up to the merged OMN-13196 OCC evidence (#2686). The omnibase_infra impl PR #2007 was rescoped to benchmark-only: the two src docstring edits (pure doc comments) were moved to B5 (OMN-13204) to keep the PR out of the deploy-gate's runtime-path matcher. The force-push moved PR #2007's head from
57f66e31f→f432045df, so the merged contract's infra check_value (which greps the old SHA) needs rebinding.What this carries
drift/dod_receipts/OMN-13196/pr-omnibase_infra/command.yaml—commit_sha+ prose updated tof432045df; scope narrowed to the perf-benchmark retarget; honesty + hardening gates pass.contracts/OMN-13196.yaml— thepr-omnibase_infracheck_value grepscommit_sha "f432045df…"(pr_number2686unchanged, dual-key).contract_sha256rebound to the yamlfmt-normalized contract (7075ac5c…).Why
The omnibase_infra
verify / verifyReceipt-Gate for PR #2007 binds the contract'scommit_shagrep to the PR head. After narrowing scope the head changed; this rebinds it so the gate passes on the new head.pr_number: 2686(original OCC PR) is retained per the dual-key the merged contract greps. verifier=receipt-gate-local (≠ runner omn-13196-impl).OMN-13196