Repository navigation
Correct guard policy documentation and prepare v0.4.1 - #6
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
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.
The README said the guard never executes tests after v0.4.0 introduced executable verification. Correct the audit and claims/strict/verify policy descriptions, put verification setup earlier, and show the controlled comparison with execution costs and evidence limits.
Prepare a documentation-only 0.4.1 patch with matching package/plugin versions so npm receives the corrected README. Update the publication records for 0.3.2 and 0.4.0. Runtime code and dependencies are unchanged.
Validation: full Node 24 test suite; npm tarball validation and isolated offline installation, including CLI/demo/diagnostics and an actual failure → repair → retest check. Registry currently serves 0.4.0. Release follows green CI → OIDC staging → maintainer npm 2FA approval → public-install verification.