evidence(OMN-16041): OCC companion for OmniNode-ai/omnibase_infra#2745

[jonahgabriel]

Manual OCC companion (non-implementer attestation batch, 2026-08-18). Net-new contract entry + receipt files only, append-only.

Cites: OMN-16041

Evidence-Source: self (this PR)

Binds OmniNode-ai/omnibase_infra#2745 (chore(OMN-16041): backmerge main lineage into dev alongside the v0.38.5 promotion) at head 50dc2fccf1fcfad39a57295dacfc8ff42f241ac4.

OMN-16041 is an existing shared-ticket contract already carrying evidence for OmniNode-ai/omniclaude#1989, #1993, and OmniNode-ai/omnibase_infra#2744 (the main-side half of the same promotion). PR #2745 is the dev-side backmerge half and had never had its own dod_evidence entry -- this PR appends one (pure addition, no existing entries touched: 1 file changed, 20 insertions(+) on the contract commit).

#2745's own PR body carries a per-file conflict-resolution decision table for the branch merge (main vs dev vs union, per path). Before minting, independently verified two of its load-bearing claims against the diff rather than trusting the table: (1) scripts/validate_handler_contracts.py took main's glob-based descriptor scan, not dev's hardcoded seven-handler list against a directory that no longer exists in either branch -- re-ran the validator against the merged tree myself, 5/5 validated, 0 failed, matching the PR's claim exactly; (2) the pyproject.toml/uv.lock version-pin conflict resolved to dev's 0.38.7 (above main's already-released 0.38.6), not main's stale 0.38.5. Also spot-checked three of the "byte-identical to origin/main" claims (validate_handler_contracts.py, env-parity.yml, util_runtime_packages.py) via a direct git diff origin/main -- zero diff on all three.

The dod_evidence entry pins both verified facts at the PR's exact head SHA via the GitHub contents API (gh api .../contents/<path>?ref=<sha> | base64 -d | grep -q <symbol>), verified admissible against the live evidence_admissibility.classify_evidence() function before authoring, and both contract_sha256/contract_entry_sha256 were computed with the real compute_contract_sha256/compute_contract_entry_sha256 functions against the committed contract. check_receipt_hardening.py exits 0.

A self-bind entry follows in a second commit once this PR's number is known.

[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: 49 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 111 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: 39d7b049-fd03-493f-9d67-ed50855a229e

📥 Commits

Reviewing files that changed from the base of the PR and between 2b50056 and 04efa6a.

📒 Files selected for processing (3)

• contracts/OMN-16041.yaml
• drift/dod_receipts/OMN-16041/dod-promotion-omnibase-infra-pr-2745/command.yaml
• drift/dod_receipts/OMN-16041/occ-self-bind-pr-6661/command.yaml

---

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

[onexbot-occ-writer]

OCC autobind stood down for OmniNode-ai/omnibase_infra#2745 (OMN-16041): this PR (hand_authored) already carries evidence for that ticket, so no competing companion was minted (OMN-15247 defer-on-contention).