test(ops): replay CDC safe observability RED on current develop

[seonghobae]

Rebuilds issue #182 from exact protected develop@1f06296faf7140eff03d069cc7def2d804c02b98 rather than rewriting stale-base Draft #297.

This replacement is intentionally test-only RED at exact source dffb4717c9558d1041503b0b62f7b70986e63530. The focused contract loads the deployable CDC base configuration and requires it not to force 100% trace sampling, application DEBUG, or Spring Web DEBUG, while requiring an explicit local profile to preserve the developer-verbose posture.

Protected source still hard-codes management.tracing.sampling.probability: 1.0, logging.level.com.xtrmetl: DEBUG, and logging.level.org.springframework.web: DEBUG in application.yml, and no protected application-local.yml exists. Hosted RED must reach those real configuration assertions; compilation/fixture/import failure is not valid RED.

After valid current-base RED, the bounded GREEN is to remove only those verbose overrides from the default profile and add application-local.yml restoring them under spring.config.activate.on-profile: local. Preserve root/debezium log levels, Zipkin destination, all other CDC configuration, standalone/MSA compatibility, and current security/coverage controls.

Keep Draft through RED → GREEN. Do not close #297 until exact diff/ancestry proves its unique three-file behavior is preserved. Stale/predecessor/synthetic-only/status-only/author-only/queued/pending/skipped-required evidence is not merge authority.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 9 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: e90f646d-f3ad-4f42-85f4-fd62935329aa

📥 Commits

Reviewing files that changed from the base of the PR and between 1f06296 and 1ab7691.

📒 Files selected for processing (3)

• cdc-service/src/main/resources/application-local.yml
• cdc-service/src/main/resources/application.yml
• cdc-service/src/test/java/com/xtrmetl/cdc/config/CdcObservabilityProfileContractTest.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.}