ci(OMN-14078): remove merge_group triggers from 15 non-required workflows (Lever 1 fan-out)

[jonahgabriel]

Summary

Lever 1 fan-out (sibling of the OMN-14076 core canary) — docs/plans/2026-07-06-ci-streamlining-logjam-reduction-plan.md §3. Removes the merge_group: trigger from 15 non-required workflows in omnibase_infra/.github/workflows/. The merge queue only waits on required status contexts; these 15 carry none, so their merge_group runs burn shared self-hosted runner slots and gate nothing. pull_request/push/workflow_dispatch triggers are untouched — nothing is un-enforced. 15 files, 17 pure deletions, no logic changes.

Closes OMN-14078

dod_evidence — independent verification against the LIVE required set

Live required contexts on omnibase_infra dev (branches/dev/protection/required_status_checks) = 15; ruleset check → [] (no ruleset-based required checks). Each required context maps to a KEPT carrier workflow:

CI Summary, Topic Enum/Naming/Drift→ci · Handler Contract Compliance→omni-standards-compliance · gate / CodeRabbit Thread Check→cr-thread-gate-caller · verify / verify→call-receipt-gate · call-reject-skip-token/...→call-reject-skip · contract-validation · receipt-honesty · URL Authority Gate→url-authority-gate · deploy-gate / deploy-gate→deploy-gate · dispatcher-route-coverage · Canonical Inference Gate→canonical-inference-gate · Dep Provenance Gate→dep-provenance-gate.

DEVIATION FROM PLAN (verified, deliberate): the plan's infra cut list (16) included omni-standards-compliance, but the live check proves that workflow produces the required context Handler Contract Compliance. Cutting its merge_group trigger would drop a required context from the queue SHA and wedge the infra merge queue. It is therefore EXCLUDED — verified cut = 15, not 16.

Post-edit proof (exactly complementary): re-parse of all workflows shows the set still carrying a top-level merge_group trigger = exactly the 12 required-context carriers (ci, call-receipt-gate, call-reject-skip, canonical-inference-gate, contract-validation, cr-thread-gate-caller, dep-provenance-gate, deploy-gate, dispatcher-route-coverage, omni-standards-compliance, receipt-honesty, url-authority-gate). No cut file retains merge_group; all cut files keep valid pull_request/push triggers and intact jobs. actionlint on all 15 edited files → no real errors (only pre-existing shellcheck style notes in untouched run: scripts).

The 15 cut workflows

call-occ-preflight, check-handshake, check-sibling-compat, compose-config-lint, dispatch-parity-gate, env-parity, fresh-deploy-fitness, lane-census-staleness, no-bare-compose-teardown, node-migration-sync, runner-disk-preflight, runner-routing-audit, skill-node-mapping-sync, validate-validator-requirements, validator-runtime-profiles.

Cannot break a required gate by construction. Trivially revertible.

Evidence-Source: OCC#3660
Evidence-Ticket: OMN-14078

Summary by CodeRabbit

• Bug Fixes / CI
  • Updated multiple automated checks to stop running on merge-queue events, ensuring they only execute on standard push/pull_request (and workflow_dispatch where configured).
  • Refreshed shared workflow timeout settings (UV_HTTP_TIMEOUT) to keep behavior consistent.
• Tests
  • Updated CI workflow-trigger validation to assert the new, merge-queue-excluded trigger contract.

[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: 30 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: c5d2e8b8-d635-4965-9438-2a430319d758

📥 Commits

Reviewing files that changed from the base of the PR and between 8b6c014 and 2be3028.

📒 Files selected for processing (1)

• .github/workflows/url-authority-gate.yml

📝 Walkthrough

Walkthrough

This PR removes merge_group triggers from multiple GitHub Actions workflows, adds workflow_dispatch to two workflows, updates two UV_HTTP_TIMEOUT environment declarations, and changes one CI test to match the new runner-disk-preflight trigger contract.

Changes

Workflow Trigger and Env Updates

Layer / File(s)	Summary
Remove merge_group triggers across workflows .github/workflows/call-occ-preflight.yml, check-handshake.yml, check-sibling-compat.yml, compose-config-lint.yml, dispatch-parity-gate.yml, fresh-deploy-fitness.yml, no-bare-compose-teardown.yml, node-migration-sync.yml, runner-disk-preflight.yml, runner-routing-audit.yml, skill-node-mapping-sync.yml, validate-validator-requirements.yml, validator-runtime-profiles.yml	Removes the merge_group event stanza from the on: block in each workflow, leaving the other configured triggers in place.
Add workflow_dispatch triggers .github/workflows/env-parity.yml, .github/workflows/lane-census-staleness.yml	Replaces the removed merge_group trigger with workflow_dispatch in the same on: block position.
UV_HTTP_TIMEOUT env updates .github/workflows/url-authority-gate.yml, .github/workflows/validate-validator-requirements.yml	Adds a duplicate top-level env block re-declaring UV_HTTP_TIMEOUT: "600" in one workflow, and updates the value in the other.
Update runner-disk-preflight trigger test tests/ci/test_runner_disk_preflight.py	Updates the workflow-trigger test to assert workflow_dispatch is present and merge_group is absent for runner-disk-preflight.yml.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• OmniNode-ai/omnibase_infra#1823: Related check-sibling-compat.yml workflow behavior change involving merge_group.
• OmniNode-ai/omnibase_infra#2192: Related runner-routing-audit.yml workflow trigger changes.
• OmniNode-ai/omnibase_infra#2209: Related trigger and concurrency changes in several of the same workflows.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: removing merge_group triggers from 15 non-required workflows.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-14078-remove-merge_group-triggers-from-non-required-workflows

---

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