test(coverage): rebuild non-vacuous JaCoCo gate on live develop

[seonghobae]

Supersedes stale/diverged PR #164 for issue #162 without transferring old-head checks or reviews.

Exact live base: develop@106add38465937f6eb4e4accc185fd30aab4446f.
Exact current test-only RED head: 9c46c91aab0f47bd398eca4a08b54822560dd529.

This first replacement commit adds only JaCoCoCoverageConfigurationTest. It requires report/check to select compiled class-file patterns rather than a plugin-level agent pattern, requires the durable-job BUNDLE rule to fail closed on zero selected production classes, and proves intended production target classes exist after compilation. Protected production configuration is intentionally unchanged, so a current-base hosted RED at the JaCoCo configuration boundary is expected before any POM repair is ported.

Keep Draft through current-base RED → narrow POM GREEN → newly exposed production branch coverage repair. The prior branch's later co-location hardening, source-local doctoring, and coverage-deficit tests must be revalidated/rebuilt only after this live-base RED is proven. Exact-source execution, scanner completeness, repository-wide owned-production scope, governance, and independent review remain separate gates.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 175c95a0-2607-4068-bda4-333dcfcd5d2c

📥 Commits

Reviewing files that changed from the base of the PR and between ae4efe6 and 1d1f62d.

📒 Files selected for processing (6)

• etl-service/pom.xml
• etl-service/src/test/java/com/xtrmetl/etl/documentation/JaCoCoCoverageConfigurationTest.java
• etl-service/src/test/java/com/xtrmetl/etl/job/EtlJobCoveragePolicyTest.java
• etl-service/src/test/java/com/xtrmetl/etl/job/EtlJobModelCoverageBoundaryTest.java
• etl-service/src/test/java/com/xtrmetl/etl/job/EtlJobServiceBoundaryTest.java
• etl-service/src/test/java/com/xtrmetl/etl/job/EtlJobServiceDefensiveBranchTest.java

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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