Repository navigation
feat: add protected Windows installation transaction - #870
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.
A protected Windows installation needs an exact account, service and file authority before the installed owner can run. This PR adds a transaction API that refuses preexisting resources, pins the created account SID and file identities, applies restricted directory/service permissions, and preserves unknown rollback states as terminal failures.
The new installer is deliberately dormant until the owner/runtime integration is reviewed separately. This PR alone does not establish E1.4, E11.2 or Windows VM acceptance. Hosted qualification must inspect the actual process token, installed ACLs, upgrade/uninstall and cleanup behavior.
Validation: 20 transaction fixture controls, one native directory-pinning test, an administrator-guard mutation RED, scoped ESLint/Prettier/PowerShell parse/counts/diff checks, and independent GPT-6.1 Sol source review. The five required exact-head CI contexts will be checked before merge.