[WP02 · SubStep 02.05] Enforce reviewed dependency admission - #19
Merged
Merged
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.
Dependency changes now require an input-bound admission review rather than only matching dependency manifests. Enforce exact locked versions, registry/integrity, first-party public import scope, immutable historical name/version integrity, reviewed upgrade gates and the existing shipped-artifact licence/provenance authorities. Preserve dependency versions and publication behavior; distinguish existing native/build-tool licences from runtime adoption.
Validated locally: 15 focused offline admission/refusal tests, existing source-provenance audit, and Git whitespace checks. No dependency or toolchain restore, product build, runtime/browser/live-provider execution or public artifact download was performed. Exact Prettier formatting passed using the existing offline cache. Existing CI remains responsible for applicable type/security/build/candidate checks.
Review follows the merged WP02.05 profile. Retain this branch/worktree. Coordinator reviews and merges after all applicable checks succeed.