test(cdc): reproduce target capability metadata gap on current develop - #312
Conversation
|
Warning Review limit reached
Next review available in: 109 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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
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. Comment |
* test(etl): reproduce HTTP payload materialization on live develop * fix(etl): bound HTTP payloads before MVC materialization * test(security): replay Jackson LTS baseline on live develop * fix(security): align Jackson with patched 2.21 LTS BOM * test(security): reject Jackson BOM decoy evidence * test(security): validate Jackson BOM structurally * test(etl): preserve payload boundary acceptance cases
Rebuilds the truthful CDC target-capability boundary from exact protected
develop@4408b6086fd725ff1629d8f048cf28f3a2b40b1bwithout transferring stale evidence from #255/#308.Exact fail-first head:
6b8caee7714fdeb57f16aa7b3688febe76e4fa8b. This intentionally adds onlyCdcTargetCapabilityTest: the productionCdcTargetConnectorat the exact base still exposesscaffoldOnly()but no machine-readablecapabilities()contract, while live Kafka and JDBC-replica product paths have intentionally unwired canonicalwrite(...)methods.Acceptance for RED: hosted CI must reach the CDC production-boundary test and fail because
CdcTargetConnector.class.getMethods()contains nocapabilitiesmethod, rather than due setup/import/fixture failure. Only after exact-head RED is proven should the narrow production capability metadata be implemented. No check/review from #255, #308, or another head transfers.