[jonahgabriel]

Summary

• stream the coverage sweep pytest subprocess output directly to CI logs
• keep the gate failure message focused on the return code now that stderr is not captured
• add a regression assertion that the gate does not redirect/capture subprocess output

Verification

• uv run pytest tests/ci/test_run_coverage_sweep_gate.py -q (9 passed; includes parent heartbeat regression)
• uv run ruff format scripts/ci/run_coverage_sweep_gate.py tests/ci/test_run_coverage_sweep_gate.py
• uv run ruff check scripts/ci/run_coverage_sweep_gate.py tests/ci/test_run_coverage_sweep_gate.py
• synthetic --skip-generate coverage sweep PASS
• hosted coverage attempt showed stream-only fix was insufficient; latest head adds parent heartbeat while pytest is quiet
• pre-commit hooks PASS with OMNIBASE_INFRA_PATH=/Users/jonah/Code/omni_home/omnibase_infra

Evidence-Ticket: OMN-14641
Evidence-Source: OCC#4227
Evidence-Commit: ea802c82cf3efd6941d569765e4ac059f2c46498
Evidence-Head: 98d9c06

[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: 28 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: 373d39c2-010c-40eb-ba11-6ce25eabf441

📥 Commits

Reviewing files that changed from the base of the PR and between f624969 and 98d9c06.

📒 Files selected for processing (2)

• scripts/ci/run_coverage_sweep_gate.py
• tests/ci/test_run_coverage_sweep_gate.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-14641-coverage-sweep-stream-output

---

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

[github-actions]

✅ Architectural Review — PASSED

Errors: 0
Warnings: 0

What this checks

Rule	Description
ARCH-TOPIC-001	No hardcoded Kafka topic strings in handler code
ARCH-DI-001	No event_bus=None bypass
ARCH-DI-002	No direct Handler instantiation outside workflow_runner/adapters
ARCH-DI-003	No reinvented DI containers
ARCH-TOPIC-002	contract.yaml topics follow `onex.{cmd

---

No architectural violations found.

Static architectural lint — no model inference (OMN-14176).

[github-actions]

✅ Hostile Reviewer — PASSED

Blocking findings (critical/error): 0
Total findings: 0
Models succeeded: qwen3-review,qwen3-review-b

---

Gate semantics (pilot phase)

Verdict	Meaning	Blocks merge?
passed	No critical/error findings	No
blocked	CRITICAL or ERROR findings found	Yes
degraded	All models unavailable (infra)	No (pilot)

Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)