[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
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 rejects unadmitted/floating dependencies, forbidden licences, internal Contracts, wrong publishers/feeds and rewritten immutable versions. The owner policy closes all 91 existing NuGet package-version identities from locks and cached published metadata. Upgrade evidence seals actual inputs, and framework baseline versions are checked against accepted Git source.
The policy runs in the existing check with retained evidence. Source adaptation uses immutable ArcNotes b7358bd, with r4 provenance superseding and preserving r1/r2/r3. Exact package versions, application behavior and existing Windows/Linux CI remain unchanged.
Validation: cache-only locked restore, targeted C# build with zero warnings/errors, all 12 offline dependency-policy tests, repository/provenance/effective declarations and whitespace review passed. No local runtime, public downloads or toolchain provisioning. Required CI remains the merge gate.