Record verified 0.3.0 public release evidence - #16
Merged
Conversation
Signed-off-by: Chris <51251284+BitL8-ByteShort@users.noreply.github.com>
BitL8-ByteShort
marked this pull request as ready for review
September 7, 2026 17:58
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.
Record the verified public 0.3.0 release after publication. Replace preparation/candidate-only support statements with the final protected-main source commit, checksum, exact platform matrix, and separate public npm/GitHub acceptance results.
The final tarball was built once in run34146977662, published unchanged to both channels, and is immutable on GitHub. Both anonymous public downloads passed the installed package, real OpenCode host and production-browser acceptance; npm integrity and a clean named install were also verified. Public verification and issue closure.
This follow-up changes only documentation. It does not rebuild, replace or republish the released package. Validation: evidence-to-document comparison, asset/link checks, whitespace check and independent Astra/high review; protected CI remains required.