Skip to content

Correct shell resolver provenance - #79

Closed
Aaronontheweb wants to merge 5 commits into
devfrom
feature/resolver-provenance-core-ci2
Closed

Correct shell resolver provenance#79
Aaronontheweb wants to merge 5 commits into
devfrom
feature/resolver-provenance-core-ci2

Conversation

@Aaronontheweb

Copy link
Copy Markdown
Owner

Supersedes #77 and #78. GitHub Actions did not enqueue validation for either prior PR's corrected head, so this fresh head ref creates a new pull-request-opened event without changing the adversarially reviewed commit.\n\nThis 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. The independent implementation and CI-fix reviews both returned GO.

@Aaronontheweb
Aaronontheweb enabled auto-merge (squash) August 6, 2026 18:53
@Aaronontheweb

Copy link
Copy Markdown
Owner Author

Superseded by #80. #80 uses a fresh single-commit SHA whose Git tree is byte-for-byte identical to this reviewed head, specifically to force a new GitHub Actions dispatch after this PR produced no Actions check suite.

auto-merge was automatically disabled August 6, 2026 19:03

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant