create-rindle 0.8.0 → 0.10.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-rindle",
-  "version": "0.8.0",
+  "version": "0.10.0",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",

package/templates/minimal/AGENTS.md

@@ -24,7 +24,7 @@ Rindle docs are served as raw markdown for LLMs: index at
 - `pnpm migrate` — one-shot `rindle migrate apply` against the unified ingress derived
   from `rindle.ncl` (the follower's `/migrate` is write-fenced). The dev loop already
   applies on boot + on every `migrations/` change.
-- `pnpm rindle:deploy` / `pnpm rindle:migrate:remote` — deploy the data tier to
+- `pnpm rindle:deploy` / `pnpm rindle:migrate:cloud` — deploy the data tier to
   Rindle Cloud (reads `rindle.ncl`, the same file `rindle up` runs locally; run
   `rindle login` once first) and push `migrations/*.sql` to the deployed master.
 

package/templates/minimal/README.md

@@ -71,14 +71,14 @@ see the rejection path (the optimistic write snaps back + a toast).
 ```bash
 rindle login                  # once — authenticate to Rindle Cloud
 pnpm rindle:deploy            # provision / re-attach the managed app (writes .rindle/cloud.json)
-pnpm rindle:migrate:remote    # push migrations/*.sql to the deployed write-master
+pnpm rindle:migrate:cloud     # push migrations/*.sql to the deployed write-master
 ```
 
 `rindle deploy` reads `rindle.ncl` and records the binding in `.rindle/cloud.json` — commit it, so
 future deploys re-attach to the same app. `followers = 1` provisions a backed-up write-master + one
-follower (`replicated`, scales 1→N in place); raise it for more read replicas (`read-scaled`);
-`localRetention = true` provisions the one-box colocated pair (`colocated`, no streaming backup —
-no durability beyond the box). That deploys the **data tier**; the
+follower (`replicated`, scales 1→N in place); raise it for more read replicas (`read-scaled`).
+Every rung ships its journal off-box — the old one-box `colocated` rung (`localRetention = true`)
+is retired, and setting that field fails the render. That deploys the **data tier**; the
 **web app** (this Vite/TanStack Start app) deploys to any Node host — configure its server with the
 one fleet ingress (`RINDLE_URL`) and SQL bearer (`RINDLE_DATABASE_TOKEN`). Query leases derive the
 public WebSocket endpoint from that same URL, so there is no browser-side topology setting whether

package/templates/minimal/package.json

@@ -14,7 +14,7 @@
     "preview": "vite preview",
     "migrate": "rindle migrate apply --dir migrations",
     "rindle:deploy": "rindle deploy",
-    "rindle:migrate:remote": "rindle migrate apply --remote",
+    "rindle:migrate:cloud": "rindle migrate apply --cloud",
     "typecheck": "tsr generate && tsc --noEmit"
   },
   "dependencies": {

package/templates/minimal/rindle.ncl

@@ -9,12 +9,13 @@
 #
 #   rindle login                  # once — authenticate to Rindle Cloud
 #   rindle deploy                 # provision / re-attach the managed app (writes .rindle/cloud.json)
-#   rindle migrate apply --remote # push migrations/*.sql to the deployed write-master
+#   rindle migrate apply --cloud  # push migrations/*.sql to the deployed write-master
 #
 # `app` becomes the cloud display name and groups every component under one app in `rindle ps`.
 # `followers = 1` maps to the cloud `replicated` rung (a separate write-master + one follower,
-# backed up; scales 1→N in place); `followers > 1` maps to `read-scaled`. `localRetention = true`
-# maps to `colocated` (one box, both processes, no streaming backup).
+# backed up; scales 1→N in place); `followers > 1` maps to `read-scaled`. Every rung ships its
+# journal off-box; the old one-box `colocated` rung (`localRetention = true`) is retired, and
+# setting that field fails the render.
 #
 # Every follower count renders a local fleet edge;
 # FOLLOWER-AFFINITY-DESIGN.md §10). `rindle dev` injects the server's unified connection from this