Skip to content

docs: scope one-line local installer#29

Open
CallmeT-ty wants to merge 1 commit into
mainfrom
docs/local-installer-scope
Open

docs: scope one-line local installer#29
CallmeT-ty wants to merge 1 commit into
mainfrom
docs/local-installer-scope

Conversation

@CallmeT-ty

Copy link
Copy Markdown
Contributor

Hand-off scope for a one-line curl … | sh installer 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 vetra from the README is broken (that npm package is an unrelated placeholder), and the real install recipe has non-obvious constraints encoded in the global-install CI job. The doc captures the evidence.

What's inside

  • Decisions already made — native global install, prompt for key-or-subscription, host TBD.
  • CI-validated install reality — tsdown-bundled CLI, deps resolve from public npm, vetra-cli only on registry.dev.vetra.io (which uplinks to public npm — verified), npm install is flag-free / pnpm needs flags.
  • Non-obvious constraints — pnpm@11.5.0 on PATH even for npm installs (ph init --pnpm), ph-cmd pin + ensure-ph safety net, global-bin-dir on PATH, required env.
  • 5 open decisions for the dev, each framed to choose — registry routing, PM choice, ph-cmd eager vs. lazy, file location/host, v1 out-of-scope (Docker, local-model, Renown deploy auth).
  • Risks — dev-registry reliance, pack-vs-publish parity, README fix.

🤖 Generated with Claude Code

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant