test(supply-chain): rebase Docker digest RED on live develop

[seonghobae]

Rebuilds the still-valid #215 supply-chain defect from exact current protected develop@106add38465937f6eb4e4accc185fd30aab4446f instead of reusing stale-base evidence from #216.

Current test-only head 9ac73aed8a9d448926739ae0c1d70ba0ed83646b adds only RepositoryDockerBaseImagePolicyTest. The test reaches the production root Dockerfile and requires each external base image to retain a readable non-latest tag plus a full lowercase SHA-256 digest. Protected source still has tag-only Maven and Temurin FROM references, so valid hosted RED must be the new policy assertion after normal compilation/test startup; setup/import/fixture/infrastructure failure is not valid RED.

After valid current-base RED, the smallest GREEN may update only the two production FROM references using freshly verified official Docker Hub multi-platform index digests. Historical #216 content may be preserved only after revalidation; no predecessor checks/reviews transfer. Keep Draft through RED/GREEN and shared exact-source, complete scanner, non-vacuous coverage, independent-review, and branch-governance gates.

Fixes #215 after protected integration. Replaces stale-base PR #216 only after unique-work preservation is proven.

[coderabbitai]

Warning

Review limit reached

@opencode-agent[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 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: a2b7b8c9-e4fd-4e2a-b6ab-69bde1373dbf

📥 Commits

Reviewing files that changed from the base of the PR and between 609b290 and cf99761.

📒 Files selected for processing (4)

• CHANGELOG.md
• Dockerfile
• docs/doctoring/docker-base-image-digest-pinning.md
• etl-service/src/test/java/com/xtrmetl/etl/config/RepositoryDockerBaseImagePolicyTest.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.}