create-clivly 0.9.0 → 0.9.2

package/README.md

@@ -40,6 +40,7 @@ validating a prerelease build.
 | `clivly.config.ts` | No — yours to edit |
 | The tick route for your framework | Yes — `--force` to overwrite |
 | The auth-verify route for your framework | Yes — `--force` to overwrite |
+| The framework boot hook, where Clivly can add one safely | Yes — `--force` to overwrite |
 
 Plus `CLIVLY_SECRET_KEY`, `CLIVLY_SYNC_TRIGGER_URL` and
 `CLIVLY_SYNC_TRIGGER_SECRET` placeholders in your framework's env file
@@ -49,6 +50,10 @@ and — unless `--no-login` — it pairs this machine with your workspace.
 It creates **no database tables** and does **not** modify your ORM schema.
 Clivly Cloud holds the CRM records; your own tables are only ever read.
 
+WebSocket presence remains an explicit runtime choice. For a long-lived Node
+host, add `presence: { transport: "websocket" }` to `clivly.config.ts`;
+serverless and edge hosts continue to use HTTP.
+
 If you run it from a workspace root, it looks for a supported Drizzle app in
 that repo and scaffolds there. If it finds more than one, it stops and shows you
 the candidate directories instead of guessing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-clivly",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "private": false,
   "type": "module",
   "description": "Scaffold Clivly into your app — the create-* entry point for `clivly init`.",
@@ -34,7 +34,7 @@
     }
   },
   "dependencies": {
-    "clivly": "0.9.0"
+    "clivly": "0.9.2"
   },
   "author": "Joseph Amani",
   "engines": {