Repository navigation
docs: prefer PyPI install in user-facing install sections - #116
Merged
Merged
Conversation
The published package is the normal user path; source checkout should stay a contributor option, not the only documented install.
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
pip install pt-snap-cliso published users are not told to clone first.pip install -e ".[dev]"note in quickstart/MCP, with English and Chinese docs aligned.Test plan
pytest tests/test_governance.pyruff check .andblack --check .pytest(769 passed; one preexisting environmental failure from ancestor.pt-snap/focus.jsonin the nested worktree)Fixes #115
📝 Description
User-facing install docs still listed only
pip install -e .after the package was published to PyPI. This PR makes PyPI the primary install command and leaves editable install as the contributor path.🔗 Related Issue
Fixes #115
🧪 Testing
✅ Checklist
Snapshot Runtime Provenance
Snapshot provenance decision: no-update
Snapshot provenance no-update reason: Documentation and governance test only; no snapshot runtime files change.