Repository navigation
evidence(OMN-15567): regenerate OCC companion for infra#2663 (occ#6177 closed unmerged) - #6289
Conversation
…7 closed unmerged) occ#6177 was CLOSED without merging (operator-approved 2026-08-08 open-PR census triage, append-only observation conflict — hand-resolution would have invalidated the prior Evidence-Source binding). The OCC Companion Merged Gate (OMN-15214) on omnibase_infra#2663 fails because it cites a closed, unmerged companion. Adds a net-new dod_evidence entry bound to #2663's CURRENT head (dabe52ddc1277e1f434b15d73a6503a0f7a74c41), superseding the last pre-closure entry. Ticket: OMN-15567
…e52dd) Ticket: OMN-15567
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 15 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 (2)
📝 WalkthroughWalkthroughThe contract adds verified bindings for infrastructure PR ChangesOMN-15567 Evidence Bindings
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Ticket: OMN-15567
Ticket: OMN-15567
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml`:
- Line 1: Rename the receipt at
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml#L1-L1 to
2026-08-10T01:24:40Z.yaml, and rename
drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml#L1-L1 to the
same timestamped filename; update receipt discovery if it relies on
command.yaml.
- Line 11: Add the SHA-256 hash of the final raw bytes of
contracts/OMN-15567.yaml as contract_sha256 in both receipts:
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml (lines
11-11) and drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml
(lines 11-11). Preserve contract_entry_sha256 as the canonical per-entry hash
and use the identical raw-contract hash value in both files.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3b48a7af-0e4f-4108-bf3c-e3750f8bfb10
📒 Files selected for processing (3)
contracts/OMN-15567.yamldrift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yamldrift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml
| @@ -0,0 +1,30 @@ | |||
| --- | |||
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift
Store each receipt at the required timestamp path.
Both receipts use command.yaml. Store each receipt as <run_timestamp>.yaml under its evidence-item directory. Update receipt discovery if it depends on the old filename.
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml#L1-L1: rename the receipt to2026-08-10T01:24:40Z.yaml.drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml#L1-L1: rename the receipt to2026-08-10T01:24:40Z.yaml.
As per coding guidelines, “Store DoD receipts only at drift/dod_receipts/<TICKET>/<ITEM_ID>/<run_timestamp>.yaml.”
📍 Affects 2 files
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml#L1-L1(this comment)drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml#L1-L1
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml` at line
1, Rename the receipt at
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml#L1-L1 to
2026-08-10T01:24:40Z.yaml, and rename
drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml#L1-L1 to the
same timestamped filename; update receipt discovery if it relies on
command.yaml.
Source: Coding guidelines
| 'if (.number == 2663 and .state == "OPEN" and .headRefName == "jonah/omn-15567-docker-build-timeout-marker" | ||
| and .headRefOid == "dabe52ddc1277e1f434b15d73a6503a0f7a74c41" and ([.files[].path] | sort) == [".github/workflows/nightly-integration.yml","tests/integration/docker/conftest.py","tests/integration/docker/test_docker_integration.py"]) | ||
| then "true" else error("unexpected #2663 current head or diff scope") end' | ||
| contract_entry_sha256: "sha256:9c9b0398e43373f810c05c213489b306468973abd4da70680ecd2553bce5a534" |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Add the raw contract hash to both receipts.
Both receipts bind contract_entry_sha256 only. Compute the SHA-256 hash from the final raw bytes of contracts/OMN-15567.yaml and add it as contract_sha256 to both receipts.
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml#L11-L11: add the final raw-contractcontract_sha256.drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml#L11-L11: add the same final raw-contractcontract_sha256.
As per coding guidelines, bind both contract_sha256 to the contract raw bytes and contract_entry_sha256 to the canonical per-entry hash.
📍 Affects 2 files
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml#L11-L11(this comment)drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml#L11-L11
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml` at line
11, Add the SHA-256 hash of the final raw bytes of contracts/OMN-15567.yaml as
contract_sha256 in both receipts:
drift/dod_receipts/OMN-15567/dod-infra-pr-2663-dabe52dd/command.yaml (lines
11-11) and drift/dod_receipts/OMN-15567/occ-self-bind-pr-6289/command.yaml
(lines 11-11). Preserve contract_entry_sha256 as the canonical per-entry hash
and use the identical raw-contract hash value in both files.
Source: Coding guidelines
jonahgabriel
added
the
ci:ready
The occ-self-bind-pr-6289 check_value hardcoded PR #6289's own head SHA (fb1afd8...), making the check unsatisfiable after any push -- a self-bind can never equal its own post-commit head. Rebinds to the loose existence/open-state probe form (verbatim pattern from occ#6288: `gh pr view <N> --repo ... --json number,state`), recomputes contract_entry_sha256 via omnibase_core.validation.validator_receipt_gate. compute_contract_entry_sha256 against the post-yamlfmt-reflow contract. Ticket: OMN-15567 Evidence-Ticket: OMN-15567
1 participant
Summary
occ#6177 was CLOSED without merging (operator-approved 2026-08-08 open-PR census
triage: append-only observation conflict — hand-resolution would have invalidated
the prior Evidence-Source binding). The OCC Companion Merged Gate (OMN-15214) on
omnibase_infra#2663fails because it cites a companion PR that is CLOSED, notMERGED — that state is terminal per
check_occ_companion_merged.py, neverresolvable by polling.
This PR regenerates the companion: a net-new
dod_evidenceentry appended tocontracts/OMN-15567.yaml, bound toomnibase_infra#2663's current headdabe52ddc1277e1f434b15d73a6503a0f7a74c41, plus its PASS receipt.Verification
omnibase_infra#2663stateOPEN, head
dabe52ddc1277e1f434b15d73a6503a0f7a74c41, and the expected 3-filediff scope — the exact command embedded as the entry's
check_value.contract_entry_sha256computed viaomnibase_core.validation.validator_receipt_gate.compute_contract_entry_sha256against the post-yamlfmt-reflow committed contract.
Ticket: OMN-15567
Evidence-Ticket: OMN-15567
Summary by CodeRabbit