docs(pi): add verified source package installation - #187
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.
Pi's npm package is still awaiting publisher account access, and the source README previously pointed at an extension command without a clone sequence while incorrectly requiring peer dependency installation. Add a pinned clone and local-path package install that loads both the extension and bundled skill in Pi 0.85.1.
Document project scope, the need to keep the clone in place, manual updates, removal, and an extension-only trial. Keep npm publication explicitly pending.
Validation: real Pi 0.85.1 installation from the merged source with no package node_modules; the guild command registered and ran without a model call or live Guild request. Pi supplies the peer dependencies. Direct Git monorepo and npm tarball-URL routes were inspected and tested and do not load this extension in that release. Documentation-only change; whitespace checks pass.