Skip to content

receipt(OMN-13501): OCC evidence for omnimarket faked-boundary burn-down (PR #1594) - #3551

Merged
jonahgabriel merged 4 commits into
devfrom
jonah/omn-13501-occ-burndown-receipts
Jul 3, 2026
Merged

jonahgabriel merged 4 commits into
devfrom
jonah/omn-13501-occ-burndown-receipts

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

OMN-13501 — OCC evidence for omnimarket faked-boundary burn-down

Net-new DoD receipts (OMN-13888 net-new-only; the OMN-13501 contract and all prior receipts are untouched) binding the omnimarket faked-boundary burn-down to OMN-13501:

  • drift/dod_receipts/OMN-13501/dod-omnimarket-pr-1594/command.yaml — binds omnimarket PR chore(occ-deps): update rerun state after 799571d6 #1594 (all 69 no-faked-boundary findings burned to zero; detector clean; full pytest 11862 passed / 60 skipped) by PR number + head commit SHA 7707f7b6.
  • drift/dod_receipts/OMN-13501/dod-occ-3551-self-binding/command.yaml — this OCC PR self-binding receipt.

Both receipts carry contract_sha256: sha256:f63451bb98a17f9a7838c69b8e438ec5ebfa11f17560adb7e8b11744248ffa9b (matches sha256(contracts/OMN-13501.yaml) at dev — contract unchanged). Receipt hardening gate passes on both; yamlfmt clean.

Companion code PR: OmniNode-ai/omnimarket#1594.

Evidence-Ticket: OMN-13501

@coderabbitai

coderabbitai Bot commented Jul 3, 2026 •

Copy link
Copy Markdown

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: 26 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: e791f93f-ca60-441f-8f2d-4aeaefd9ab80

📥 Commits

Reviewing files that changed from the base of the PR and between a206c38 and 8b10f63.

📒 Files selected for processing (7)
  • contracts/OMN-13501.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-3551-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-13501/dod-omnimarket-pr-1594/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-13501-occ-burndown-receipts

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

@jonahgabriel
jonahgabriel enabled auto-merge July 3, 2026 18:24
…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
@jonahgabriel
jonahgabriel added this pull request to the merge queue Jul 3, 2026
Merged via the queue into dev with commit 8aca276 Jul 3, 2026
42 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-13501-occ-burndown-receipts branch July 3, 2026 20:28
jonahgabriel added a commit that referenced this pull request Sep 22, 2026
…infra#3551 (#10834)

* evidence(OMN-16964): retire the citation of closed-unmerged omnibase_infra#3551

#3551 closed unmerged on 2026-09-16 and was rebuilt as #3644 (merged,
a8f5d576). Its two generated dod_evidence items still cite it as active,
so the done-flip gate reads a closed PR as outstanding evidence and
refuses OMN-16964 even though AC1-AC4 rest on merged PRs.

Append-only: a -superseded contract entry plus its PASS receipt, whose
check proves #3551 is CLOSED and never merged and #3644 is MERGED
(negative control with an unmerged PR in place of #3644 exits 1). The
entry states plainly that the rebuild is not byte-equivalent.

Onex-Lane: m4-probes-tag
Onex-Session: e9212aee28a44af79f587bf255185029

* evidence(OMN-18921): mint the owed OCC self-bind for PR #10834

---------

Co-authored-by: onexbot-occ-writer[bot] <onexbot-occ-writer[bot]@users.noreply.github.com>
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