docs: migrate all config install commands to CLI format

Replace curl commands with 'openboot install' across all documentation:
- quick-start.md, personal.md, teams.md
- custom-configs.md, snapshot.md, config-options.md
- api-reference.md, faq.md
- README.md, AGENTS.md

Assumes users have OpenBoot CLI installed (per landing page flow).
Keeps curl only for initial OpenBoot installation itself.

Simplifies user experience: 38% shorter commands, clearer intent.

Author: fullstackjam

AGENTS.md

@@ -7,7 +7,7 @@
 ## OVERVIEW
 
 Web dashboard and install API for OpenBoot. SvelteKit 5 + Cloudflare Workers + D1 (SQLite).
-Serves config pages, install scripts (curl|bash), dashboard UI, OAuth login, and docs.
+Serves config pages, install API, dashboard UI, OAuth login, and docs.
 
 ## STRUCTURE
 

README.md

@@ -10,7 +10,7 @@
 
 - **Landing page** — product overview, presets, install commands
 - **Dashboard** — create, edit, duplicate, and share custom configs
-- **Install script API** — generates per-config install scripts for `curl | bash`
+- **Install API** — serves configs for the OpenBoot CLI
 - **Brewfile import** — parse and convert Brewfiles into OpenBoot configs
 - **Homebrew search** — live package search from the dashboard
 - **CLI auth** — device flow for authenticating the CLI via browser

src/docs/api-reference.md

@@ -355,7 +355,7 @@ Configs have three visibility levels that control access:
 | **unlisted** | Anyone with link can view | Anyone can install | Anyone can read |
 | **private** | Owner only | Requires auth | Owner only |
 
-For private configs via `curl | bash`, the install script automatically opens the browser for authentication.
+For private configs, run `openboot login` first to authenticate before installing.
 
 ---
 

src/docs/config-options.md

@@ -103,7 +103,7 @@ Snapshot data attached to this config (auto-populated when creating from `openbo
 
 ### `alias`
 
-Short URL alias for easy sharing. If set, the config is accessible at `openboot.dev/<alias>` — for example, `curl -fsSL https://openboot.dev/my-setup | bash`.
+Short URL alias for easy sharing. If set, the config is accessible with a shorter command — for example, `openboot install my-setup` instead of `openboot install username/slug`.
 
 - **Type:** string
 - **Required:** no
@@ -118,7 +118,7 @@ Controls who can see and install this config.
 - **Options:**
   - `"public"` — listed on your profile, install URL works for everyone
   - `"unlisted"` — not listed on your profile, but install URL still works if shared
-  - `"private"` — only you can access. Via `curl | bash`, the script opens a browser for authorization. Via the CLI, run `openboot login` first, then `openboot --user yourname/slug`
+  - `"private"` — only you can access. Run `openboot login` first, then `openboot install yourname/slug`
 
 ## Export
 

src/docs/custom-configs.md

@@ -38,18 +38,12 @@ Already have a Brewfile? Upload it in the dashboard. OpenBoot parses all `brew`
 
 Every config gets a URL:
 
-```
-curl -fsSL https://openboot.dev/sarah/frontend-team/install.sh | bash
+```bash
+openboot install sarah/frontend-team
 ```
 
 Put it in your README, onboarding docs, or Slack. One command, same environment for everyone.
 
-You can also install via the CLI directly:
-
-```
-openboot --user sarah/frontend-team
-```
-
 ## Visibility
 
 Every config has a visibility setting you can change in the dashboard:
@@ -62,17 +56,11 @@ Every config has a visibility setting you can change in the dashboard:
 
 ### Installing Private Configs
 
-**Via `curl | bash`** — the install script automatically opens your browser for authorization, then proceeds with the install:
+Run `openboot login` first to authenticate, then install as usual:
 
-```
-curl -fsSL https://openboot.dev/yourname/my-setup/install.sh | bash
-```
-
-**Via the CLI** — run `openboot login` first, then use `--user` as usual. The CLI sends your auth token automatically:
-
-```
+```bash
 openboot login
-openboot --user yourname/my-setup
+openboot install yourname/my-setup
 ```
 
 ## Short URLs

src/docs/faq.md

@@ -22,7 +22,7 @@ If you're happy managing each of those separately, you don't need OpenBoot. If y
 **Use Homebrew** (`brew install openboot`) if you:
 - Already have Homebrew installed
 - Want cleaner updates (`brew upgrade openboot`)
-- Prefer package managers over `curl | bash`
+- Prefer package managers and the OpenBoot CLI over ad-hoc scripts
 
 **Use the one-line installer** if you:
 - Don't have Homebrew yet (it installs Homebrew for you)
@@ -42,7 +42,9 @@ Fair question. Here's how OpenBoot handles it:
 - You can inspect the script before running it:
 
 ```bash
-curl -fsSL https://openboot.dev/install.sh > install.sh && cat install.sh
+curl -fsSL https://openboot.dev/install.sh > install.sh
+cat install.sh  # Review the script
+bash install.sh  # Run it after review
 ```
 
 If you prefer, install via Homebrew instead (see above).

src/docs/personal.md

@@ -84,7 +84,7 @@ Everything that isn't a package — directory structure, SSH keys, repo cloning
 When the new machine arrives, or when IT finally sends that hardware refresh email:
 
 ```bash
-curl -fsSL https://openboot.dev/alex/my-setup/install.sh | bash
+openboot install alex/my-setup
 ```
 
 Everything restored. Twenty minutes, done.

src/docs/quick-start.md

@@ -81,10 +81,10 @@ Snapshot scans your Homebrew packages, macOS preferences, shell config, and git
 🎯 Launching editor...
 ```
 
-After uploading, you get a shareable URL:
+After uploading, you get a shareable install command:
 
-```
-curl -fsSL https://openboot.dev/yourname/my-setup/install.sh | bash
+```bash
+openboot install yourname/my-setup
 ```
 
 See [Snapshot](/docs/snapshot) for the full walkthrough.
@@ -98,16 +98,10 @@ If you're setting up a team's standard environment:
 
 ```bash
 brew tap openbootdotdev/tap && brew install openboot
-openboot --user yourteam/frontend
-```
-
-Or use the one-line installer as an alternative:
-
-```bash
-curl -fsSL https://openboot.dev/yourteam/frontend/install.sh | bash
+openboot install yourteam/frontend
 ```
 
-3. **New team members** run the commands and get your exact setup
+3. **New team members** run the command and get your exact setup
 
 See [For Teams](/docs/teams) for the complete workflow.
 

src/docs/snapshot.md

@@ -60,8 +60,8 @@ curl -fsSL https://openboot.dev/install.sh | bash -s -- snapshot
 
 If you upload, you'll authenticate via browser (like `gh auth login`), name your config, and get a one-line install command:
 
-```
-curl -fsSL https://openboot.dev/yourname/my-setup/install.sh | bash
+```bash
+openboot install yourname/my-setup
 ```
 
 ## Flags

src/docs/teams.md

@@ -20,7 +20,7 @@ OpenBoot replaces The Doc with one command.
 Your new hire opens the `CONTRIBUTING.md`. Step one:
 
 ```bash
-curl -fsSL https://openboot.dev/acme/frontend/install.sh | bash
+openboot install acme/frontend
 ```
 
 That's the entire setup section. They run it and go read the architecture docs while packages stream by:
@@ -88,7 +88,7 @@ Add the install command to your `CONTRIBUTING.md`:
 ```markdown
 ## Development Setup
 
-    curl -fsSL https://openboot.dev/acme/frontend/install.sh | bash
+    openboot install acme/frontend
 
 Or install via Homebrew: