@lotics/cli 0.164.0 → 0.171.0

package/README.md

@@ -36,18 +36,39 @@ package (reachable at `node_modules/@lotics/cli/docs/*.md` once installed):
   workspace facts an agent can't guess, the access-vs-activation model, and the
   catalog-then-stage retrieval model agents use to pull only the lines they need.
 
-## Install
+## Start from a starter, in one command
+
+Install the CLI, then copy a starter — it creates the account, copies the starter into its
+workspace, deploys the app, and prints a one-time sign-in link:
 
 ```bash
-npm install -g @lotics/cli
+curl -fsSL https://lotics.ai/install.sh | bash
+lotics start <starter_id> --email you@company.com
 ```
 
-## Update
+The installer downloads one compiled executable — no Node.js, no npm. Copying a starter is the
+one step that needs more: it builds the app locally, and building needs Node 18+.
+
+Add `--json` for one machine-readable object instead of progress — the organization, the
+workspace, the app id, what was created, the sign-in link, and any warnings. Already signed in?
+Drop `--email` and `lotics start <starter_id>` copies into the account you have.
+
+## Install
 
 ```bash
-npm install -g @lotics/cli@latest
+curl -fsSL https://lotics.ai/install.sh | bash    # macOS, Linux, WSL — no Node.js needed
+npm install -g @lotics/cli                        # or, if you already have Node 18+
 ```
 
+```powershell
+irm https://lotics.ai/install.ps1 | iex           # Windows PowerShell — no Node.js needed
+```
+
+## Update
+
+Re-run whichever installer you used; `npm install -g @lotics/cli@latest` updates an npm install.
+The CLI names the right one for the copy you are running when it sees a newer version.
+
 The CLI checks for updates once per day and prompts when a new version is available.
 
 ## Authentication