Correct shell resolver provenance - #80
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
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.
Supersedes #77, #78, and #79 after GitHub Actions failed to dispatch for their corrected or reused heads. This branch is a single clean commit whose Git tree is byte-for-byte identical to the fully validated and adversarially approved 4916e70 tree.\n\nThe change preserves literal, typed-expansion, and opaque fragment provenance through Bash and PowerShell resolution; applies explicit native, cmdlet, redirect, Path, and LiteralPath contexts; corrects oracle-proved false classifications; and keeps unknown forms fail-closed.\n\nLocal validation: Release build with zero warnings, 1,120 tests, focused security and live-shell oracle matrices, public API and PII gates, headers, formatting, Slopwatch, strict OpenSpec validation, and diff hygiene. Independent implementation and CI-fix reviews both returned GO.