Skip to content

receipt(OMN-13501): add omnimarket deploy assessment evidence - #3537

Merged
jonahgabriel merged 6 commits into
devfrom
jonah/omn-13501-deploy-evidence
Jul 3, 2026
Merged

jonahgabriel merged 6 commits into
devfrom
jonah/omn-13501-deploy-evidence

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

Summary

Adds deploy-assessment DoD evidence for OMN-13501 / omnimarket#1590 so deploy-gate can verify the runtime-path touch.

Evidence-Source: OCC#3536
Evidence-Ticket: OMN-13501

Verification

  • uv run validate-yaml contracts/OMN-13501.yaml
  • uv run python -m onex_change_control.scripts.validate_pr_contracts --diff-files contracts/OMN-13501.yaml drift/dod_receipts/OMN-13501/dod-deploy-assessment/command.yaml
  • uv run python -m omnibase_core.validation.validator_receipt_honesty --receipts-dir drift/dod_receipts drift/dod_receipts/OMN-13501/dod-deploy-assessment/command.yaml
  • uv run python scripts/validation/check_receipt_hardening.py drift/dod_receipts/OMN-13501/dod-deploy-assessment/command.yaml

@coderabbitai

coderabbitai Bot commented Jul 3, 2026 •

Copy link
Copy Markdown

Review Change Stack

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: 48 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: fc7e1d57-ba22-4460-b79d-59281b07eefd

📥 Commits

Reviewing files that changed from the base of the PR and between c9a9889 and 9759abe.

📒 Files selected for processing (16)
  • contracts/OMN-13501.yaml
  • contracts/OMN-13894.yaml
  • contracts/OMN-13898.yaml
  • drift/dod_receipts/OMN-13501/dod-deploy-assessment/command.yaml
  • drift/dod_receipts/OMN-13501/dod-occ-3537-self-binding/command.yaml
  • drift/dod_receipts/OMN-13501/dod-occ-self/command.yaml
  • drift/dod_receipts/OMN-13501/dod-omnimarket-pr-1590/command.yaml
  • drift/dod_receipts/OMN-13894/dod-occ-3537-self-binding/command.yaml
  • drift/dod_receipts/OMN-13894/dod-omniclaude-deploy-assessment/command.yaml
  • drift/dod_receipts/OMN-13894/dod-omniclaude-pr-1844/command.yaml
  • drift/dod_receipts/OMN-13898/dod-core-promotion-pr/command.yaml
  • drift/dod_receipts/OMN-13898/dod-occ-self-binding/command.yaml
  • drift/dod_receipts/OMN-13898/dod-omniclaude-bump-pr/command.yaml
  • drift/dod_receipts/OMN-13898/dod-omniclaude-deploy-assessment/command.yaml
  • drift/dod_receipts/OMN-13898/dod-omniintelligence-bump-pr/command.yaml
  • drift/dod_receipts/OMN-13898/dod-omnimemory-bump-pr/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-13501-deploy-evidence

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

@jonahgabriel
jonahgabriel enabled auto-merge July 3, 2026 13:14
@jonahgabriel
jonahgabriel force-pushed the jonah/omn-13501-deploy-evidence branch 5 times, most recently from c2da4fa to d97bd43 Compare July 3, 2026 13:36
@jonahgabriel
jonahgabriel force-pushed the jonah/omn-13501-deploy-evidence branch from d97bd43 to 82d2b47 Compare July 3, 2026 13:46
@jonahgabriel
jonahgabriel added this pull request to the merge queue Jul 3, 2026
@jonahgabriel
jonahgabriel removed this pull request from the merge queue due to a manual request Jul 3, 2026
@jonahgabriel
jonahgabriel enabled auto-merge July 3, 2026 13:54
@jonahgabriel
jonahgabriel added this pull request to the merge queue Jul 3, 2026
@jonahgabriel
jonahgabriel removed this pull request from the merge queue due to a manual request Jul 3, 2026
@jonahgabriel
jonahgabriel added this pull request to the merge queue Jul 3, 2026
@jonahgabriel
jonahgabriel removed this pull request from the merge queue due to a manual request Jul 3, 2026
@jonahgabriel
jonahgabriel enabled auto-merge July 3, 2026 14:11
@jonahgabriel
jonahgabriel added this pull request to the merge queue Jul 3, 2026
Merged via the queue into dev with commit 2953aa6 Jul 3, 2026
41 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-13501-deploy-evidence branch July 3, 2026 14:21
jonahgabriel added a commit that referenced this pull request Jul 3, 2026
…amp contract_sha256

Fixes the pr_ticket_mismatch that blocked BOTH omnimarket PR #1594 (occ-preflight/eligibility,
verify) and this OCC PR #3551 (self-eligibility): the OMN-13501 contract declared evidence only
for PR #1590/#3537, so the receipt-gate eligibility loop (which iterates contract-declared
dod_evidence items) never checked the net-new burn-down receipts and found no PR-#1594/#3551-bound
PASS receipt.

- Append two dod_evidence items to contracts/OMN-13501.yaml: dod-omnimarket-pr-1594 (binds code
  PR #1594) and dod-occ-3551-self-binding (binds this OCC PR #3551).
- Whole-file contract hash changes on append (f63451bb -> 05ecb897), so re-stamp contract_sha256
  in all six receipts to the new hash — the exact pattern merged OCC #3537 used when it added the
  deploy-assessment evidence item. Receipt semantics are unchanged; only the hash pointer updates.

Verified locally with validator_occ_merge_eligibility: PR#3551 and PR#1594 both eligible=True
(present, PASS, hash-bound, PR-bound). yamlfmt idempotent; all OCC pre-commit gates pass
(Receipt Honesty Gate, Receipt Hardening Gate, dod_evidence required, contract YAML schema).

Evidence-Ticket: OMN-13501
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant