Rate of Closure: harden Windows authority state - #4392
Draft
d-sorgcodexagent[bot] wants to merge 3 commits into
Draft
Rate of Closure: harden Windows authority state#4392d-sorgcodexagent[bot] wants to merge 3 commits into
d-sorgcodexagent[bot] wants to merge 3 commits into
Conversation
added 3 commits
August 12, 2026 07:38
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.
Outcome
Implements the Windows authority-state ACL and reparse hardening tracked by #4385 as an exact child of PR #4391.
Security contract
Local evidence
Release blocker
This PR intentionally targets only
[self-hosted, Windows, X64, d-sorg-windows-security]. No registered runner currently carries that restricted label. The protected native matrix must remain queued until such a runner is provisioned; do not route it to the persistent ControlTower/MATLAB runner or weaken the contract.Human review is approved. Parent order, fresh protected CI, and ordinary non-admin merge behavior remain mandatory.