Repository navigation
receipt(OMN-13762): bind infra dev-promotable receipt to promotion PR #2164 - #3390
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 49 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates two DoD receipt YAML files for OMN-13762. One receipt gains a new ChangesDoD Receipt Metadata Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
…6 -> 2026-09 The three jonah-owned LEGACY_MIGRATION exceptions expired at the June->July rollover, failing check-db-boundary-registry on every OCC dev PR. Extend the owner's own review window to unblock the release cascade.
Every bound check was executed for real in the omni_worktrees/closer-coverage omnibase_infra checkout at PR #3390 head b370ab699, with OMNI_HOME resolved to that worktree root so the contract's cwd is the branch under review. Ten checks, ten exit-0 runs, recorded across eight receipts keyed by item and check type. Each carries the per-entry contract hash (OMN-13888) and not the legacy whole-file one, and each probe_command opens with a repos/OmniNode-ai/omnibase_infra commit resolution so the commit_sha gate can resolve a sha that lives in the product repo rather than this one. AC6's second check was rewritten before minting. It previously ran 'gh pr checks 3390', which cannot be green until this companion merges, so no receipt could honestly record it; it now reads both halves of the node_version pinning instead.
#8890) * evidence: OCC companion pass 1 for OmniNode-ai/omnibase_infra#3390 * evidence: OCC companion self-bind for #8890 * evidence(OMN-18125): bind AC1-AC6 to the checks that prove them Six dod_evidence items carrying binds_ac, one per criterion, executed at cwd ${OMNI_HOME}/omnibase_infra. Every bound pytest node id was resolved and run green in the OMN-18125 worktree before this contract was written; the two grep controls and the changed-file assertion were run there too. No merged item is edited. The four auto-minted items are untouched. * evidence(OMN-18125): committed receipts for the six AC-bound items Every bound check was executed for real in the omni_worktrees/closer-coverage omnibase_infra checkout at PR #3390 head b370ab699, with OMNI_HOME resolved to that worktree root so the contract's cwd is the branch under review. Ten checks, ten exit-0 runs, recorded across eight receipts keyed by item and check type. Each carries the per-entry contract hash (OMN-13888) and not the legacy whole-file one, and each probe_command opens with a repos/OmniNode-ai/omnibase_infra commit resolution so the commit_sha gate can resolve a sha that lives in the product repo rather than this one. AC6's second check was rewritten before minting. It previously ran 'gh pr checks 3390', which cannot be green until this companion merges, so no receipt could honestly record it; it now reads both halves of the node_version pinning instead. --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@omninode.ai> Co-authored-by: jonahgabriel <jonah@omninode.ai>
1 participant
Summary
Bind
dod-infra-dev-promotable-to-mainto the omnibase_infra dev->main promotion PR #2164 bypr_number. The promotion carries 195+ commits, exceeding GitHub's 100-commit PR-commits API cap, so commit_sha binding cannot resolve — pr_number binding is required for occ-preflight eligibility.Receipt-only edit (no contract change; contract_sha256 stays 740bfed6). dod-occ-self rebound to this OCC PR.
Evidence-Ticket: OMN-13762
Evidence-Source: OCC#3384
dod_evidence
dod-occ-self: PASS — this OCC PR carries the pr_number binding for the infra promotion.Summary by CodeRabbit