evidence(OMN-14394): OCC companion for omnibase_infra PR 2266

[jonahgabriel]

Summary

OCC companion for omnibase_infra PR #2266 (OMN-14394), authored under the OMN-14055 independent-verifier escape hatch (verifier != implementer, no self-authoring). Product PR: fix(OMN-14394): close pr_state is_draft seam gap + dict-envelope regression test.

Note on merge order: #2266 is a STACKED PR — base is jonah/omn-14375-github-state-projection-pr-state (#2262/OMN-14375, currently open and OCC-cascade-blocked itself), not dev. This companion clears #2266's own occ-preflight eligibility now so it is merge-ready the moment #2262 lands and GitHub retargets #2266's base to dev. #2266 cannot merge before that happens.

Verification performed (independent, not self-attested)

• Confirmed gh pr diff 2266 is a clean stacked delta — only the is_draft additions (migration 092+rollback, 4 src files, 3 test files), no bleed from fix(OMN-12766): correct dishonest PASS receipts to PENDING on OCC dev #2262's own content.
• Confirmed migration 092 is collision-free: dev has 090, fix(OMN-12766): correct dishonest PASS receipts to PENDING on OCC dev #2262's branch adds 091, release(OMN-12765): promote OCC dev evidence to main #2266's branch adds 092 — sequential, no dupe.
• Confirmed the seam match field-for-field: ModelPayloadPrStateUpsert.is_draft: bool = False (producer, non-nullable) matches omnimarket's ModelOpenPrSummary.is_draft: bool (reader, required, non-nullable) — no type/nullability mismatch — plus the SQL column BOOLEAN NOT NULL DEFAULT false.
• Independently reproduced RED->GREEN in a fresh worktree: reverse-patched the 4 touched src files against the post-fix tests -> 9 failed, 47 passed; restored -> 56 passed, matching the PR body's claims exactly.
• Confirmed the HandlerPrStateProjection god-class ratchet holds at exactly 10 sync methods (the inlined bool-coercion approach, no new sibling method).

Files (all net-new, append-only per OMN-13888)

• contracts/OMN-14394.yaml
• drift/dod_receipts/OMN-14394/dod-omnibase-infra-pr-2266-head-daa28e5c/command.yaml
• drift/dod_receipts/OMN-14394/dod-deploy-assessment-head-daa28e5c/command.yaml
• drift/dod_receipts/OMN-14394/dod-occ-self-commit/command.yaml

Adversarial invariants

• runner: fix-14394 / verifier: verify-14394 — distinct identities, neither denylisted, so PASS status is not auto-downgraded to ADVISORY by ModelDodReceipt.enforce_adversarial_invariants().
• contract_sha256 on every receipt = sha256:d988ab7aa858dbc480ea9863512f77a612296964c545145ca4c10230ae646a39, computed from the post-yamlfmt formatted contract and verified stable across both evidence commits.

Local gates

• uv run pre-commit run --files contracts/OMN-14394.yaml drift/dod_receipts/OMN-14394/**/*.yaml — all hooks passed, including Receipt Honesty Gate and Receipt Hardening Gate (OMN-13060).
• uv run validate-yaml contracts/OMN-14394.yaml — [OK] (ticket_contract).

Hard limits observed

• Did not merge this PR.
• Did not stamp release(OMN-12765): promote OCC dev evidence to main #2266's body (Evidence-Commit needs the OCC merge commit, which doesn't exist yet).
• Touched no files outside OMN-14394's own contract/receipt paths.

OMN-14394

[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: 35 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: 807bd4be-909b-40f4-9d7b-c4162a51d672

📥 Commits

Reviewing files that changed from the base of the PR and between 9466ee7 and e4858f3.

📒 Files selected for processing (4)

• contracts/OMN-14394.yaml
• drift/dod_receipts/OMN-14394/dod-deploy-assessment-head-daa28e5c/command.yaml
• drift/dod_receipts/OMN-14394/dod-occ-self-commit/command.yaml
• drift/dod_receipts/OMN-14394/dod-omnibase-infra-pr-2266-head-daa28e5c/command.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-14394-occ-pr2266

---

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