Repository navigation
docs: correct bilingual CLI and Python installation - #2
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
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.
Change
Replace the unavailable npm CLI install and unrelated Python package with the published binary installer and paired pinned Python SDK archives. Explain PATH setup and Windows terminal refresh in both languages.
Validation
Three posts validate with zero problems; English/Chinese source snapshots are synchronized to the companion website branch. Actual Linux binary installer and paired Python source install were independently executed successfully. Public install scripts returned HTTP 200 and match the reviewed CLI source. The paired Python archive pin is identical across the three repositories.
Limits
No macOS/Windows native execution or production deployment was performed. Browser OS selection and asset availability are not native-platform execution. No package publication is claimed. No secrets or credential files are included.
Repository-owned installation decision and verification evidence are now included under
.agents/. Latest local validation again checks 3 posts with zero problems. The record commit needs its own remote CI result before merge.