fix(cdc): rebuild secure DDL object default on live develop

[seonghobae]

Replacement execution lane for #233 from exact live protected develop@106add38465937f6eb4e4accc185fd30aab4446f, preserving #234 history without rewriting it.

TDD evidence is now current-base complete on exact head 785dbef9132a2649a17c3565c49f85ee5e24d619:

• RED head e1076270d8b8944a3afc6fe08464d324c5d21448 changed only XtrmetlPropertiesSecurityDefaultTest; hosted CI reached the real XtrmetlProperties.Replica boundary and failed because the Java object returned none instead of whitelist.
• GREEN commit changes only XtrmetlProperties.Replica.ddlValidationMode from none to whitelist; ddlEnabled remains false and explicit operator selection of supported validation modes is unchanged.
• Hosted CI on the current synthetic merge of 785dbef... into 106add... passes on macOS, Ubuntu and Windows; Dependency Review, SBOM, SAST and Security Scan also pass. The focused regression test passes in the full CDC reactor run.

Keep Draft. The shared repository coverage control remains independently non-passing as commercial evidence because current CI still reports JaCoCo Analyzed bundle 'etl-service' with 0 classes and then vacuously says all checks were met; active coverage repair #284 owns that boundary. Qualifying independent non-author approval and the remaining shared source/governance gates must be revalidated on the unchanged final head before integration.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 18 seconds

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: 64107835-33f0-44c8-b64f-58f9e2914d28

📥 Commits

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

📒 Files selected for processing (2)

• cdc-service/src/main/java/com/xtrmetl/cdc/config/XtrmetlProperties.java
• cdc-service/src/test/java/com/xtrmetl/cdc/config/XtrmetlPropertiesSecurityDefaultTest.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.}

[seonghobae]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.