adapto-install

# adapto:install The global bootstrap — like `npm create`. It makes the toolchain ready, then hands off to the right setup skill. It writes **no CMS content** (`mutates: false`), but it does perform **host-level** changes (installing/upgrading the CLI), which are gated by explicit consent. ## When to use - First-time setup / **the front door**: "set up adapto", "get started", "adapto init". It preflights (`adapto:doctor`), ensures the CLI, then routes to `adapto:scaffold`. (No separate `adapto:init` — this is it.) - The `adapto` CLI is missing or out of date (e.g. `adapto:doctor` flagged it). - Starting a new Adapto project. ## When not to use - Routine content/schema/translation work → the specific skill. - Only checking whether things are OK → `adapto:doctor` (read-only; it never installs anything). ## Inputs - New project vs existing repo (auto-detect from cwd; confirm with the user). - New projects: framework (`next` | `astro` | `sveltekit`) and, optionally, a public API key. - Optional: a specific CLI version to install (defaults to the supported baseline, `>=0.1.3`). ## Outputs - `adapto` CLI installed and at/above the baseline, **verified** via `adapto version`. - The user routed to `adapto:scaffold` to create a new project. - (v1, spec-level) per-repo skill pack installed under `.claude/skills/` + `.adapto/skills.lock` pins. ## Preconditions - A shell, network, and `curl` or `wget`. Node 20+ for the `create-adapto-app` path. - **Does NOT require the CLI** — in...