Analyze New-Module initialization regions - #110
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.
Adds the bounded PowerShell New-Module execution-region state slice for the accepted v0.3 OpenSpec.
New-Module script blocks are analyzed as synchronous once-only initialization from caller state in a child module scope. Ordinary child bindings are restored, location outcomes are shared, and exported command identities invalidate later unqualified commands. Common variable-writing parameters are applied before the module body, including conservative command-resolution invalidation for preference-variable targets. Canonical, alias, and supported module-qualified forms share the same mutation identity.
Security regressions cover common writer families, module-autoload preference changes, module-qualified Function-provider exports, pipeline interleaving, shared location, host outcome joins, and child-scope isolation. Live PowerShell probes cover ReturnResult, writer initialization, pipeline staging, scope, aliases, and location behavior.
Validation: Release build clean; 2,142 tests pass; header verification; strict OpenSpec validation; Slopwatch zero issues. Adversarial review GO on staged SHA-256 3e1b7b9a62631db9a604f32308a87a71bb156ffec5f424d6825a4c7c62373247 after three concrete blocker/fix/review cycles.