[WP02 · SubStep 02.05] Enforce desktop dependency admission and upgrade evidence - #9
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.
The desktop consumer now refuses unadmitted or floating dependencies, forbidden licences, internal Contracts and wrong publisher/feed identities. The owner policy closes all 91 existing NuGet package-version identities using committed locks and cached published metadata, while a reviewed input record requires scoped upgrade evidence and framework-major runtime assessment. Historical Git admissions prevent new reviews from changing bytes under an existing version.
The gate runs in the existing repository check and writes retained CI evidence. Exact dependency versions, product behavior, current Windows/Linux CI and publication mechanisms are unchanged.
Validation: cache-only locked restore, targeted C# build (zero warnings/errors), 12 offline dependency-policy cases, repository/provenance/effective declaration check, and whitespace review passed. No local runtime, public artifact downloads or toolchain provisioning were performed. Required CI remains the merge gate.