ci(OMN-13875): CI Summary directly gates Contract Compliance Check

[jonahgabriel]

OMN-13875 — omnibase_infra finding #3

Problem

Contract Compliance Check (contract-compliance) was not a direct input to the required CI Summary. It only reached the aggregate via detect-changes/test-parallel (both list it in needs). When contract-compliance fails, GitHub marks those dependents skipped; CI Tests Gate tolerates test-parallel == skipped (the legitimate docs-only path), and CI Summary never referenced contract-compliance — so a contract-compliance failure slipped through with CI Summary green. Same class as OMN-13873.

Fix

Add contract-compliance directly to ci-summary.needs and to its pass condition as success || skipped, plus report it in both summary branches.

Wedge-safety

contract-compliance's job if: is pull_request || merge_group || push and it carries no path/zone filter, so on every gating event (incl. docs-only PRs) it runs and is never skipped. The skipped tolerance only covers non-gating events (workflow_dispatch), so no failure slips via skipped and no docs-only PR is wedged. CI Summary is the required context (verified via branch protection).

Verification

Workflow-YAML-only change (no Python touched). Validated via yaml.safe_load (OK) + targeted pre-commit run --files .github/workflows/ci.yml (applicable hooks Passed) + the live CI run on this PR.

Evidence-Source: OCC#3523
Evidence-Ticket: OMN-13875

[coderabbitai]

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: 56 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: 3faed2d1-60bd-4e58-b5a9-8816c6ee07ab

📥 Commits

Reviewing files that changed from the base of the PR and between b0d9e5d and a905586.

📒 Files selected for processing (1)

• .github/workflows/ci.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-13875-infra-ci-summary-contract-compliance

---

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