Record the v3.15.1 audit entry - #146
Merged
Merged
Conversation
No four-corpus audit: the release changes only how a preview is reported. Both published executables reproduce byte-for-byte from a fresh clone of the tag, the release run's driven hash matches, both report 3.15.1, and both archive hashes match GitHub's digests. Records that one evidence step first read another run's artifact and was corrected by the release run's own ID, and the limits: unsigned by decision, no accessibility spot check, preview export not seen live, self-contained executable not driven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Docs only: the
docs/SAFETY-AUDIT.mdrecord for v3.15.1, written after the tag as the release checklist requires.v3.15.1match the published ones; the release run's driven hash matches; both report3.15.1; both archive hashes match GitHub's digests.0efbc5f6…); fetching by the release run's own ID gave the matching hash. The mismatch was in the collection, not the release.🤖 Generated with Claude Code