test(coverage): reproduce repository-wide coverage authority gap

[seonghobae]

Purpose

Advance #205 test-first from protected develop@8f96517987cf2cab4398696503b22a131a4b66a6 by proving the repository-wide owned-production coverage authority gap before changing build or production configuration.

Exact scope

• Head before PR creation: eeb5f4f99f524ae1bc47189c9f2e7aaaf998d688
• Base before PR creation: develop@8f96517987cf2cab4398696503b22a131a4b66a6
• Test-only change: RepositoryCoverageAuthorityTest
• No production source, Maven coverage configuration, workflow, or documentation changes in this commit.

Expected RED

The new contract inventories the live Maven reactor and owned src/main/java tree. It must fail on the current base because:

1. cdc-service, config-server, eureka-server, and zuul-gateway have owned production Java but no executable JaCoCo coverage authority.
2. etl-service has a non-vacuous strict gate only for the durable-job slice, while other owned ETL production classes remain outside that selected scope.
3. A compliant module must fail closed when zero production classes are selected and must enforce zero missed instruction, line, method, and branch counters.

The RED is valid only if hosted CI compiles the repository normally and failure reaches these new assertions. Setup/compile/infrastructure failure is not accepted as evidence.

Standards basis

JaCoCo's Maven plug-in provides prepare-agent, check, and aggregate/reporting capabilities; current upstream documentation is the implementation authority for the eventual remediation. The canonical doctoring evidence remains a separate documentation lane because the active docs spine must not be raced.

References (APA 7th):

• JaCoCo. (2026). JaCoCo Maven Plug-in. https://www.jacoco.org/jacoco/trunk/doc/maven.html
• JaCoCo. (2026). JaCoCo check Maven goal. https://www.jacoco.org/jacoco/trunk/doc/check-mojo.html
• JaCoCo. (2026). JaCoCo report-aggregate Maven goal. https://www.jacoco.org/jacoco/trunk/doc/report-aggregate-mojo.html

Closes no issue yet. #205 remains open until repository-wide exact 100% owned-production statement/branch authority is implemented and proven on the integrated protected head.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a2bb0b79-36d1-4095-8c99-4aa68b14fcc6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}