ci: bridge native ADLC required check context - #187
Merged
huijoohwee merged 1 commit intoSep 4, 2026
Conversation
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
1 participant
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.
Expose
adlc-policy-contractalongside the currently required legacy context so the provider can migrate without losing its validation gate. Both workflows reuse the existing validation result, including exact-candidate authorization for protected refresh.Validation: full
npm test; 29 focused migration/refresh tests; GitHub Actions reports both contexts successful on the exact candidate. The bridge is retired by the following native-policy change.Lane: agent/huis-macbook-pro-3.local/adlc-check-context-bridge
Base-Revision: c6a5e9f
Source-Head: f4db06e