Skip to content

evidence(OMN-14104): bind OCC-first CI gating - #3673

Merged
jonahgabriel merged 3 commits into
devfrom
jonah/omn-14104-occ-first-ci-gating-evidence
Jul 7, 2026
Merged

jonahgabriel merged 3 commits into
devfrom
jonah/omn-14104-occ-first-ci-gating-evidence

Conversation

@jonahgabriel

Copy link
Copy Markdown
Contributor

Summary

  • Adds central OMN-14104 contract and PASS receipts for the OCC-first CI fanout process change.
  • Binds the pushed downstream branch heads for omnimarket, omnibase_core, omnibase_infra, and omniclaude.

Verification

  • find drift/dod_receipts/OMN-14104 -name "*.yaml" -print | xargs uv run python scripts/validation/check_receipt_hardening.py --contracts-dir contracts
  • Workflow syntax/actionlint evidence is recorded in dod-workflow-syntax.

Deploy

  • No live deploy, restart, .201 mutation, or runtime change.

OMN-14104

@coderabbitai

coderabbitai Bot commented Jul 7, 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: 18 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: 8df0ea33-a3c1-4aa1-b567-49e6198603c6

📥 Commits

Reviewing files that changed from the base of the PR and between 9112e5c and 1325448.

📒 Files selected for processing (7)
  • .github/workflows/omni-standards-compliance.yml
  • contracts/OMN-14104.yaml
  • drift/dod_receipts/OMN-14104/dod-deploy-scope/command.yaml
  • drift/dod_receipts/OMN-14104/dod-downstream-branch-heads/command.yaml
  • drift/dod_receipts/OMN-14104/dod-occ-self/command.yaml
  • drift/dod_receipts/OMN-14104/dod-workflow-syntax/command.yaml
  • tests/test_check_receipt_hardening.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jonah/omn-14104-occ-first-ci-gating-evidence

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

@jonahgabriel
jonahgabriel force-pushed the jonah/omn-14104-occ-first-ci-gating-evidence branch 3 times, most recently from 5d00aff to 8d93897 Compare July 7, 2026 14:05
@jonahgabriel
jonahgabriel force-pushed the jonah/omn-14104-occ-first-ci-gating-evidence branch from 8d93897 to 1325448 Compare July 7, 2026 14:14
@jonahgabriel
jonahgabriel merged commit 1567541 into dev Jul 7, 2026
63 of 66 checks passed
@jonahgabriel
jonahgabriel deleted the jonah/omn-14104-occ-first-ci-gating-evidence branch July 7, 2026 14:28
jonahgabriel added a commit to OmniNode-ai/omniclaude that referenced this pull request Jul 9, 2026
## Summary

Gate omniclaude CI fanout behind OCC preflight so OCC eligibility fails
before runner-heavy validation starts.

## Changes
- Adds `occ-preflight` as the first CI dependency.
- Makes quality, security, tests, build/deploy, and summary paths depend
on OCC eligibility.
- Guards top-level `always()` aggregators so they do not run after OCC
failure.

## Test plan
- [x] `actionlint -shellcheck= .github/workflows/ci.yml`
- [x] `ruby -ryaml -e YAML.load_file(ARGV[0]) .github/workflows/ci.yml`
- [x] `git diff --check`
- [x] OCC evidence: OmniNode-ai/onex_change_control#3673

## Type safety checklist
- [x] No new `metadata["key"]` or `metadata.get("key")` string literal
access on Pydantic model fields
- [x] No new `metadata: dict[str, Any]` fields without TypedDict or `#
ONEX_EXCLUDE:` comment
- [x] No new bare `except Exception` — must use narrowed type, or
minimal-scope boundary with `logger.exception(...)` + degrade comment,
or typed wrap/re-raise
- [x] If adding a key to a metadata dict, the key is defined in the
relevant TypedDict

## Related issues
OMN-14104

Evidence-Source: OCC#3674

Evidence-Ticket: OMN-14104


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Added a centralized preflight check across many workflows to run
before validation, security, test, and deploy steps.
* Improved workflow consistency by making key checks wait for the same
prerequisite gate.

* **Bug Fixes**
* Reduced the chance of downstream jobs running before required checks
complete.
* Tightened execution order and success conditions for several pipeline
stages.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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