evidence(OMN-15703): OCC companion for OmniNode-ai/omnibase_infra#2657

[jonahgabriel]

What

OCC evidence companion for OmniNode-ai/omnibase_infra#2657 (OMN-15703 — point-in-time mitigation: bump the stale hardcoded omnimarket CI fallback pin, .github/workflows/ci.yml:2330, from 4637e625 (2026-07-30) to 54356a83... (omnimarket dev HEAD as of 2026-08-03)).

I am NOT the implementer of infra#2657 — this is a net-new-file-only companion authored by a separate agent, per repo convention.

Evidence

• Content-bound probe: 54356a831e3d8876c69373cac884a3df2a5653f7 present in .github/workflows/ci.yml at infra PR docs(OMN-13172): refresh onex_change_control documentation #2657 head (09ad929d), absent (grep count 0) at infra dev HEAD (234f7bd4, still carries the stale 4637e625 pin) — confirms the bump is real and unmerged upstream.
• Product-diff-scope check: PR docs(OMN-13172): refresh onex_change_control documentation #2657 touches exactly one file, .github/workflows/ci.yml, +1/-1.
• Independently verified by a separate agent (probe-delta-0804, not this PR's runner) re-running all 3 probe commands live and confirming PASS on each — satisfies the Receipt Honesty Gate's runner != verifier requirement.

Dual-binding note: the two dod-...-pr-2657* receipts bind commit_sha to the code PR's head (09ad929d...) for the code-side verify / verify gate; a follow-up commit will add an occ-self-bind-pr-<this-PR> receipt/evidence item binding pr_number to this OCC PR's own number, for the OCC PR's own occ-preflight / eligibility self-check.

Evidence-Ticket: OMN-15703

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b01f6efa-ddf9-4c7c-8394-50dc7a5fb39d

📥 Commits

Reviewing files that changed from the base of the PR and between a3573aa and e3a3fc2.

📒 Files selected for processing (5)

• contracts/OMN-15703.yaml
• drift/dod_receipts/OMN-15703/dod-OmniNode-ai-omnibase_infra-pr-2657-ci/command.yaml
• drift/dod_receipts/OMN-15703/dod-OmniNode-ai-omnibase_infra-pr-2657/command.yaml
• drift/dod_receipts/OMN-15703/dod-occ-evidence-admissibility-validator/command.yaml
• drift/dod_receipts/OMN-15703/occ-self-bind-pr-6076/command.yaml

---

_{Comment @coderabbitai help to get the list of available commands.}