[jonahgabriel]

What

OCC companion for omnibase_core PR #1389 (OMN-13927 receipt-attestation diff-consistency gate). Net-new only: adds contracts/OMN-13927.yaml + two receipts under drift/dod_receipts/OMN-13927/. No existing contract or receipt is modified.

• dod-omnibase-core-pr-1389 — binds code PR fix(OMN-11752): route OCC rerun state through PR #1389 (23 golden/unit tests incl. receipt(OMN-13501): OCC evidence for omnimarket faked-boundary burn-down (PR #1594) #3551 must-FAIL / receipt(OMN-13888): OCC evidence for per-entry receipt hashing PRs #3548 must-PASS; 200 existing receipt/honesty/model tests pass unchanged; commit_sha d228b315).
• dod-occ-self — self-binding: pins the first commit of this OCC PR so occ-preflight resolves a PASS receipt without pre-guessing the PR number.

Verification

• uv run validate-yaml contracts/OMN-13927.yaml → OK (ticket_contract)
• pre-commit (yamlfmt, receipt-honesty, check_value lint) green on the changed files
• contract_sha256 in both receipts = sha256:ddc518a0… (contract digest after yamlfmt)

Evidence-Ticket: OMN-13927

[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: 4f229496-3ab0-49e2-9b8a-9c117006ebca

📥 Commits

Reviewing files that changed from the base of the PR and between 28791ad and 8b4a6a6.

📒 Files selected for processing (3)

• contracts/OMN-13927.yaml
• drift/dod_receipts/OMN-13927/dod-occ-self/command.yaml
• drift/dod_receipts/OMN-13927/dod-omnibase-core-pr-1389/command.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-13927-occ-evidence

---

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

[jonahgabriel]

Auto-merged by merge-sweep | correlation_id: 5c2bab15-cf3a-40bc-bfce-513a1e8a6a04

[jonahgabriel]

Auto-merged by merge-sweep | correlation_id: 5987bf85-c096-498b-aba1-90b9c5bfb910

[jonahgabriel]

Auto-merged by merge-sweep | correlation_id: 5987bf85-c096-498b-aba1-90b9c5bfb910

[jonahgabriel]

Auto-merged by merge-sweep | correlation_id: 5987bf85-c096-498b-aba1-90b9c5bfb910

[jonahgabriel]

Auto-merged by merge-sweep | correlation_id: 5987bf85-c096-498b-aba1-90b9c5bfb910