docs: scope one-line local installer#29
Open
CallmeT-ty wants to merge 1 commit into
Open
Conversation
Hand-off scope for a curl|sh installer that runs the local stack with Claude API-key or subscription auth. Captures the CI-validated global install recipe, the non-obvious constraints (pnpm-on-PATH, ph-cmd pin, PATH/env), and the open decisions a dev needs to make. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Hand-off scope for a one-line
curl … | shinstaller that gets someone from nothing to a running local Vetra stack (REPL + embedded Reactor + Switchboard + Studio), authenticated against Claude via API key or subscription.Adds INSTALLER_SCOPE.md. No code changes — this is a decision-ready scope for a dev to pick up.
Why a scope, not just a script
The "obvious"
npm install -g vetrafrom the README is broken (that npm package is an unrelated placeholder), and the real install recipe has non-obvious constraints encoded in theglobal-installCI job. The doc captures the evidence.What's inside
vetra-clionly onregistry.dev.vetra.io(which uplinks to public npm — verified), npm install is flag-free / pnpm needs flags.ph init --pnpm),ph-cmdpin +ensure-phsafety net, global-bin-dir on PATH, required env.🤖 Generated with Claude Code