evidence(OMN-14367): OCC companion for infra#2311 + omnimarket#1765 tenant-stamp reconciliation

[jonahgabriel]

Summary

Central OCC evidence companion for the second (gateway) half of the
OMN-14367 tenant-stamp reconciliation. OMN-14367 already had a contract on
dev from omnibase_infra#2257 (the shared stamp_verified_tenant_slug
helper), which explicitly flagged gateway (#2252) adoption and the
omnimarket xfail flip as separate paired follow-ups. This PR appends the
evidence closing that gap:

• dod-gateway-reconcile — verifies OmniNode-ai/omnibase_infra#2311
  (HandlerConsumeInbound.consume_inbound now routes through the shared
  helper instead of hand-building the UUID+extra-key payload)
• dod-seam-test-flip — verifies OmniNode-ai/omnimarket#1765 (the strict
  xfail on the #2252 shape flips to a genuine pass against the real
  ModelDelegateSkillRequest consumer model)
• dod-deploy-assessment-002 — deploy-surface assessment for both (no
  runtime/topic/migration change)

A self-bind receipt (dod-occ-self-002) referencing this commit's SHA
follows in a second commit so occ-preflight eligibility does not require
predicting the OCC PR number.

Local validation

• uv run validate-yaml contracts/OMN-14367.yaml: PASS
• check_receipt_hardening.py on all three new receipts: PASS
• pre-commit run on staged files: PASS

Evidence target

• Product PR: OmniNode-ai/omnibase_infra#2311
• Product head: 40a9ca2c33f76891858b4a66f8e147e34d79af35
• Product PR: OmniNode-ai/omnimarket#1765
• Product head: 116a26c47cd378f9e4362e1d02af913d503eb9cc
• Ticket: OMN-14367

[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: 11 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: 9d549047-a522-4376-a1ab-eb48ba8cd04d

📥 Commits

Reviewing files that changed from the base of the PR and between ccedd22 and 82935b0.

📒 Files selected for processing (6)

• contracts/OMN-14367.yaml
• drift/dod_receipts/OMN-14367/dod-current-2311-1765-product-observed/command.yaml
• drift/dod_receipts/OMN-14367/dod-deploy-assessment-002/command.yaml
• drift/dod_receipts/OMN-14367/dod-gateway-reconcile/command.yaml
• drift/dod_receipts/OMN-14367/dod-occ-self-002/command.yaml
• drift/dod_receipts/OMN-14367/dod-seam-test-flip/command.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-14367-occ-companion-2311-1765

---

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