chore: MIT licensing, community docs and v0.2.0 release preparation - #46
Merged
Conversation
Declare MIT consistently across Cargo, npm and Tauri; include the project license in application resources and verify its contents during bundle smoke tests. Restore the documented pnpm package entry point and document release provenance checks.
Explain verified setup and first-use commands, distinguish published builds from candidates, document security reporting and contribution expectations, and record actual distribution availability. Prepare release notes without claiming unperformed native package acceptance.
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.
Changes
Validation
Release gate
Prepare a draft release from the final main commit and its verified artifacts. Packaged GUI/PTY/hostile-browser manual acceptance on Linux and macOS is not recorded; do not claim it passed or publish without the maintainer acceptance required by docs/RELEASE_CHECKLIST.md. No release publishing workflow or signing secrets are added.