Skip to content

evidence(OMN-13226): publisher self-hosted-reroute follow-up receipt - #2766

Merged
jonahgabriel merged 4 commits into
devfrom
jonahgabriel/omn-13226-occ-publisher-reroute
Jun 18, 2026
Merged

jonahgabriel merged 4 commits into
devfrom
jonahgabriel/omn-13226-occ-publisher-reroute

Conversation

@jonahgabriel

@jonahgabriel jonahgabriel commented Jun 18, 2026 •

Copy link
Copy Markdown
Contributor

OCC evidence: OMN-13226 publisher self-hosted-reroute follow-up

Central evidence PR for the OMN-13226 follow-up (omnimarket PR #1270) that routes the merge-triggered pr-merged publisher to the self-hosted omnibase-ci runner + local lane broker, fixing the OMN-13008 / OMN-13226 live blocker.

Adds to contracts/OMN-13226.yaml:

Evidence-Source: OCC#2766
Evidence-Ticket: OMN-13226

@jonahgabriel
jonahgabriel enabled auto-merge June 18, 2026 20:21
@coderabbitai

coderabbitai Bot commented Jun 18, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

@jonahgabriel, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 hours, 38 minutes, and 56 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c2f5ad5b-11c3-4382-8a6d-6bcbb83c5098

📥 Commits

Reviewing files that changed from the base of the PR and between 4287841 and d0565b1.

📒 Files selected for processing (5)
  • contracts/OMN-13226.yaml
  • drift/dod_receipts/OMN-13226/dod-001-publisher-implementation/command.yaml
  • drift/dod_receipts/OMN-13226/dod-002-deploy-evidence/command.yaml
  • drift/dod_receipts/OMN-13226/dod-003-publisher-reroute/command.yaml
  • drift/dod_receipts/OMN-13226/pr-occ-binding/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonahgabriel/omn-13226-occ-publisher-reroute

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

@jonahgabriel
jonahgabriel added this pull request to the merge queue Jun 18, 2026
Merged via the queue into dev with commit b1423a6 Jun 18, 2026
42 checks passed
@jonahgabriel
jonahgabriel deleted the jonahgabriel/omn-13226-occ-publisher-reroute branch June 18, 2026 20:31
jonahgabriel added a commit that referenced this pull request Aug 17, 2026
#6612)

* evidence(OMN-16115): hand-authored OCC companion for OmniNode-ai/omnibase_infra#2766

The occ-autobind born-path event was swallowed at the consumer for this PR.
The original PR-open trigger (job 95292560731, run 31997821498, 05:26:34Z)
published event_id 92e8286a-2ecf-43fa-9bd4-6605dee28bd3 -- but BEFORE the PR
was retitled to carry the OMN-16115 ticket token, so that event never named
a ticket at all. One authorized workflow_dispatch replay after the retitle
(event_id 871d0f42-f3e0-4437-87c6-4153f5ca89f4, 12:54:48Z, confirmed
published to onex.cmd.omnimarket.occ-autobind.v1 on the dev-lane broker)
produced no companion after 30+ minutes. Hand-authored per controller
authorization, on the OMN-16112/occ#6589 and OMN-16114/occ#6595
manual-companion precedent.

Two content-bound, admissible-from-the-start probes (learned from the
OMN-16112/occ#6589 lane's Contract Compliance Check BLOCK on bare
`gh pr view` evidence): dod-OmniNode-ai-omnibase_infra-pr-2766 confirms
`async def run_worker_loop(` landed in
scripts/edge_delegation_worker/worker_cycle.py at #2766's head
(ebd4c098fef2eea1fa9f2df6217429436e627192), RED-verified against the PR's
base ref (a5945502fa170805c2fce9247c8be58eac657374, where the file 404s
entirely). dod-OmniNode-ai-omnibase_infra-pr-2766-ci confirms the PR's
actual diff file list via pulls/2766/files, RED-verified against a
fabricated file list. Both SIGPIPE-safe per OMN-15411 Rule E (producer
output buffered into a shell variable before the grep -q consumer reads
it, occ#5496/#5523 repair idiom) and both re-executed directly (exit 0)
against the final staged receipt bytes. contract_sha256/
contract_entry_sha256 computed via the canonical
omnibase_core.validation.validator_receipt_gate hashers.

* evidence(OMN-16115): self-bind OCC companion PR #6612

OCC companion PR #6612 -- self-bind for OMN-16115, mirroring the
occ-self-bind-pr-6595 shape. validator_occ_merge_eligibility requires at
least one PASS receipt on the cited ticket to bind to the OCC PR carrying
the evidence, otherwise the companion is ineligible with reason
pr_ticket_mismatch. contract_sha256 recomputed for all three receipts
against the contract bytes with the self-bind entry added;
contract_entry_sha256 for the two pre-existing items is unchanged
(per-entry hash is position-independent, OMN-13888).
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