Skip to content

evidence(OMN-14696): OCC Evidence-Source autobind for OmniNode-ai/omnibase_infra#2321 - #4301

Merged
jonahgabriel merged 3 commits into
devfrom
auto/omninode-ai-omnibase_infra-pr-2321-occ-autobind
Jul 17, 2026
Merged

jonahgabriel merged 3 commits into
devfrom
auto/omninode-ai-omnibase_infra-pr-2321-occ-autobind

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

Autobind OCC evidence for OMN-14696.

Triggered by node_pr_lifecycle_fix_effect OCC companion emitter on OmniNode-ai/omnibase_infra#2321 (OMN-13317 F1 / OMN-14285).

Evidence-Ticket: OMN-14696

Codex Merge Controller added 2 commits July 16, 2026 17:50
…fra#2321

OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head 9f6ab14b6cd5bdceb22437e3d9f1563532ec0049.
@coderabbitai

coderabbitai Bot commented Jul 17, 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: 7 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: 01910db2-3809-461a-88f0-11f668788b5c

📥 Commits

Reviewing files that changed from the base of the PR and between 64d65a1 and 61c0b09.

📒 Files selected for processing (4)
  • contracts/OMN-14696.yaml
  • drift/dod_receipts/OMN-14696/dod-OmniNode-ai-omnibase_infra-pr-2321-ci/command.yaml
  • drift/dod_receipts/OMN-14696/dod-OmniNode-ai-omnibase_infra-pr-2321/command.yaml
  • drift/dod_receipts/OMN-14696/occ-self-bind-pr-4301/command.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch auto/omninode-ai-omnibase_infra-pr-2321-occ-autobind

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

@jonahgabriel
jonahgabriel merged commit 07b380c into dev Jul 17, 2026
69 of 72 checks passed
@jonahgabriel
jonahgabriel deleted the auto/omninode-ai-omnibase_infra-pr-2321-occ-autobind branch July 17, 2026 01:07
jonahgabriel pushed a commit that referenced this pull request Oct 6, 2026
…301 behaviour proof (#13038)

* evidence(OMN-19978): Postgres-free successor for the omnibase_infra#4301 behaviour proof

The 2026-10-05T16:49Z sweep (comment a05be266, onex_change_control#12900)
fails only dod-occ-diff-derived-behavior-proof-pr-4301: a test_passes item
that runs four pytest files with uv in an unpinned omnibase_infra checkout,
one of which needs a Postgres server (initdb), a git checkout and
.proof-dependencies, so a bare closer host cannot pass it.

Append dod-omn19978-pr4301-proof-no-postgres, which supersedes it with a
command check pinned to commits and needing only gh: at omnibase_infra
6b97547573 (the merge commit of #4301) the two vendored
usage-by-model-day migration files hash to the sha256 values the shipped
vendor test pins, equal the omnimarket source files at 02acdb34b9
(omnimarket#3073's merge), and the application-migrations ledger carries
both tenant rows. Receipt captured with check_receipt_hardening.py
--capture-probe --red-ref 0607e9c383 (green exit 0, red exit 1: the parent
has no vendored files). No existing item or receipt is edited.

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

---------

Co-authored-by: Lakshman Patel <Lakshmanp230@gmail.com>
Co-authored-by: onexbot-occ-writer[bot] <onexbot-occ-writer[bot]@users.noreply.github.com>
jonahgabriel pushed a commit that referenced this pull request Oct 7, 2026
…loser resolves (#13133)

* evidence(OMN-19978): rerun the #4301 proof behind a first token the closer resolves

The successor merged in #13038 never ran. Its check_value opens with a
shell function definition, R(), and node_dod_verify's evidence collector
judges the first non-assignment token before executing anything: 'R' is
not on PATH, so the 10:26Z sweep marked it INVALID_CHECK_VALUE_NOT_A_COMMAND
and the original pr-4301 proof stayed failed. OCC's own check_value lint
accepted the same string, which is how it merged.

This appends one item that supersedes it, carrying the identical probe
behind `gh --version >/dev/null &&`. Checked against the collector's own
_invalid_check_value_reason (omnimarket origin/dev 9ecca9b1e): None for the
new value, the 'R' rejection for the old one. The probe exits 0 at
6b97547573 and 1 at its parent 0607e9c383 (captured), and 1 when one
pinned hash digit is changed. The collector walks supersession chains to
the terminal item, so this one verdict retires both earlier items.

Onex-Lane: omn19978-supersede-scope-superseder
Onex-Session: e72e9157-677b-4b13-bd77-daa2be198c16

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

---------

Co-authored-by: Lakshman Patel <Lakshmanp230@gmail.com>
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