feat(sandbox): build and verify patch-validator image - #67
Closed
seonghobae wants to merge 216 commits into
Closed
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
This was referenced Aug 10, 2026
This was referenced Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded historical predecessor
This branch is retained as historical lineage only and must not be merged.
Canonical successor PR #407 has now been integrated into protected
mainas squash commit8ce7c7536888ec0b596e18368eedd9379deec64fafter exact-head Application CI, reviewer-ci, central Security Scan, and the dedicatedpatch-validator-imageworkflow all reached terminal success with zero unresolved review findings.Historical identity:
feat/patch-validator-image-supply-chainabc038ce48266b93df112df4d9541dad90fa640cfeat/quarantined-patch-validationat5c2e6762d07598094e5301c491d15ba83dcdcd51mainat8ce7c7536888ec0b596e18368eedd9379deec64fA final semantic comparison against the integrated successor confirms the valuable patch-validator image/runtime/supply-chain surface remains present in protected main: exact-head image workflow, Dockerfiles, static runtime, validator runtime/profile, reviewer image integration, receipt/SBOM/scanner verification, supply-chain documentation, and the patch-validator regression families. The two historical
docs/superpowers/...design/plan artifacts do not appear as removed differences, while the integrated successor contains substantial additional hardening.Historical checks or reviews on this PR do not transfer authority to protected main; #407 supplied its own exact-head and protected-base evidence. This PR is therefore closed as superseded rather than merged.
Related: #5, #9, #66, #407.