railcode 0.1.13 → 0.1.16

package/README.md

@@ -18,7 +18,8 @@ on your `PATH`.
 
 ```
 railcode login [--api-url <url>]   Sign in and mint a personal API token
-railcode init <app> [--template static|react]
+railcode login --setup-token <token>  Sign in with a one-time onboarding setup token
+railcode init <app> [--template react|static]
 railcode deploy                    Build (if configured) and deploy the app here
 railcode db <list|query> ...       List data connectors / run read-only SQL
 ```
@@ -28,13 +29,26 @@ railcode db <list|query> ...       List data connectors / run read-only SQL
   personal API token, resolves your organization, and saves everything to
   `~/.railcode/config.json` (dir `0700`, file `0600`). The JWT is used once and
   never stored.
-- **`init <app>`** scaffolds a directory. The default `--template static` creates a
+- **`login --setup-token <token>`** is the non-interactive onboarding path (no
+  TTY or browser — used by the dashboard's copied setup prompt). A setup token
+  (`rc_setup_...`) is a short-lived (~10 min), ONE-TIME bootstrap credential, not
+  a personal API token: the CLI exchanges it once for a personal API token and
+  writes the same config as a browser login. If it's expired or already used,
+  generate a fresh prompt from the dashboard.
+- **`init <app>`** scaffolds a directory. By default it creates a React + Vite +
+  Zustand starter — a personalized "Welcome to Railcode, `<name>`" home wired to
+  every SDK capability: identity/team, a live to-dos list and file uploads (work
+  with zero setup), and SQL, saved queries, service connectors, and LLM cards that
+  call the real thing when configured and fall back to a labeled sample otherwise.
+  Hovering a name or card title reveals the exact SDK call behind it; every write
+  fires a toast with the call that just ran. Use `--template static` for a
   no-build `index.html` (loads `/_api/sdk.js` and demos `await me()` +
-  `db.collection().put/get`) plus `railcode.json` with `"dist": "."`. Use
-  `--template react` for a React + Vite + Zustand starter that builds to `dist/`.
+  `db.collection().put/get`) plus `railcode.json` with `"dist": "."`.
 - **`deploy`** reads `railcode.json` (`{ app, build?, dist? }`), runs the resolved
-  build command when needed, then uploads the output dir. The app is
-  created-or-resolved by slug in your saved org, and the live URL is printed.
+  build command when needed, then uploads the output dir by app slug. On the first
+  successful deploy for a slug, the server creates the app as part of that deploy;
+  a failed first deploy does not leave a visible not-deployed app behind. The live
+  URL is printed after success.
 - **`db`** inspects the org's **data connectors** (per-org Postgres) and runs
   ad-hoc read-only SQL. It works straight after `railcode login` — **no app and no
   `railcode.json` required** — since connectors are org-scoped; it hits the app-less