fix(audit): make post-release validation evidence authoritative#38
Merged
Conversation
Use recorded exit codes as the source of truth for validation reports. Compile backend Python files from the correct working directory, prevent E2E execution without verified process provenance, and harden audit bundle creation against recursive copies and macOS metadata. Addresses GS-IND-001 through GS-IND-006.
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.
Summary
Repairs the post-release audit tooling defects identified during the
independent Ghost Sweep v0.1.2 audit.
Findings addressed
Key changes
Validation
Validation evidence:
/Users/thor/Downloads/ghost-sweep-audit-tooling-validation-20260711-072150/Out of scope
This pull request is ready for owner review but is not authorized for merge.
Made with Cursor