Stage Windows primitive; OPE2-00126/00127 protect production#263
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why
Windows package-manager shims are batch programs; executing arbitrary batch content would reinterpret user arguments. This PR supplies narrowly recognized native launch-plan groundwork without a generic shell fallback.
This remains staged only: OPE2-00126 and OPE2-00127 must adopt the primitive before production Claude or ACP launches are protected.
Exact accepted scope
Validation
The local host cannot execute the Windows test target because it lacks a Windows execution platform; exact-head Windows CI and two fresh independent parent reviews remain required before merge.