fix(cdc): rebuild truthful target capabilities on protected develop

[seonghobae]

Stack/base repair

This Draft non-destructively rebuilds the bounded target-capability slice from exact protected develop@942d164ceb7af497bb28a95f842db96429d1bdc4. Old PR #249 remains preserved; its source head f2fd61a50c028535ec30a92d1751e6bf419b1fc4 diverges from current protected develop (ahead 4 / behind 1, merge base c2511f6b9d716ef9ab8de60a91fffd826714a4c5), so its stale-base checks and evidence do not transfer.

TDD phase

Exact first head 5d801c934a8b2d3003abb96ddc422f320c542757 adds only CdcTargetCapabilityTest. The test reaches the CDC target SPI via reflection and requires machine-readable execution capabilities for the existing Kafka and JDBC-replica targets. Production CdcTargetConnector.capabilities() is intentionally absent on the protected base, so the required first result is RED at that production boundary. Import, dependency, fixture, or runner failure does not qualify.

After a valid exact-head RED, restore only the three bounded production SPI files from #249, rerun exact-head validation, and prove semantic/file equivalence before considering #249 superseded. The HTTP controller projection remains outside this PR because its writer lane is separate. No force-push, destructive rebase, protection weakening, stale evidence transfer, or cross-repository write is permitted.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 54 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: e828fb15-8472-4d92-896f-254e28dbbb15

📥 Commits

Reviewing files that changed from the base of the PR and between 942d164 and bd0c9ad.

📒 Files selected for processing (4)

• cdc-service/src/main/java/com/xtrmetl/cdc/spi/CdcTargetConnector.java
• cdc-service/src/main/java/com/xtrmetl/cdc/spi/JdbcReplicaCdcTargetConnector.java
• cdc-service/src/main/java/com/xtrmetl/cdc/spi/KafkaCdcTargetConnector.java
• cdc-service/src/test/java/com/xtrmetl/cdc/spi/CdcTargetCapabilityTest.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.