@tomorrowos/sdk 0.7.9 → 0.8.0

package/REPLIT_SETUP.md

@@ -12,6 +12,7 @@ When a human pastes a prompt like this, **read this file and start Question 1 im
 ```text
 Follow @tomorrowos/sdk REPLIT_SETUP.md and set up my TomorrowOS CMS.
 Ask only the questions listed in REPLIT_SETUP.md, in order. Do not use LLM_PROMPT.md.
+After all setup questions are answered (including Cloudinary Secrets if you chose Cloudinary), configure and start — minimal verification only (Web app type + Preview at /). No Supabase or WebSocket tests.
 Do not skip steps.
 ```
 
@@ -35,16 +36,19 @@ Replit Agent must ask **only** the questions defined in **this file**, in **this
 | 1 | **Question 1** — How many screens / devices? | Always |
 | 2 | **Question 2** — Supabase connection | Only if answer to Q1 is **> 5** |
 | 3 | **Question 3** — Media storage (Cloudinary vs Object Storage) | Always (after Q1 or Q2) |
+| 3b | **Question 3b** — Cloudinary credentials (Secrets) | **Mandatory** if Q3 answer is Cloudinary / yes — **before Q4** |
 | 4 | **Question 4** — Brand / TomorrowOS app look | Always last, before execution |
 
 **That is the complete list.** There are no other setup questions.
 
+**Critical:** Question 3 is **not complete** when the user says “Cloudinary” or “yes”. You **must** run **Question 3b** and collect `CLOUDINARY_CLOUD_NAME`, `CLOUDINARY_API_KEY`, and `CLOUDINARY_API_SECRET` (as Replit Secrets) **before** asking Question 4. Do **not** skip to branding with placeholder or invented credentials.
 
-If the user volunteers extra info early (e.g. brand name before Q4), **record it** and still ask the current question’s required fields you do not yet have. Do not skip ahead to execution until Q1–Q4 (or Q1, Q3, Q4 if ≤5 screens) are complete.
+
+If the user volunteers extra info early (e.g. brand name before Q4), **record it** and still ask the current question’s required fields you do not yet have. Do not skip ahead to execution until Q1–Q4 (or Q1, Q3, Q3b, Q4 if ≤5 screens and Cloudinary) are complete.
 
 If the user says “just set it up, don’t ask questions,” respond:
 
-> I need four quick answers from REPLIT_SETUP.md (screen count, media storage, and branding). It takes about a minute and ensures the CMS deploys correctly on Replit.
+> I need a few quick answers from REPLIT_SETUP.md (screen count, media storage — plus Cloudinary credentials if you choose Cloudinary — and branding). It takes about a minute and ensures the CMS deploys correctly on Replit.
 
 Then ask **Question 1** — do not switch to `LLM_PROMPT.md`.
 
@@ -52,24 +56,21 @@ Then ask **Question 1** — do not switch to `LLM_PROMPT.md`.
 
 ## Hard rules
 
-1. **Ask only REPLIT_SETUP.md questions 1–4** (see **Questionnaire scope**). Never use `LLM_PROMPT.md` on Replit.
-2. **One question at a time.** Wait for the user’s answer before asking the next question (unless they already answered several in one message).
+1. **Ask only REPLIT_SETUP.md questions 1–4 and 3b when required** (see **Questionnaire scope**). Never use `LLM_PROMPT.md` on Replit.
+2. **One question at a time.** Wait for the user’s answer before asking the next question (unless they already answered several in one message). **Exception:** Question 3b may ask for all three Cloudinary Secrets in one message — still **stop and wait** for the user’s values before Question 4.
 3. **Do not invent** screen counts, Cloudinary credentials, Supabase URLs, or brand colours.
 4. **Do not use Replit’s reserved `DATABASE_URL` Secret for Supabase.** On Replit, `DATABASE_URL` is often pre-claimed. Always use **`SUPABASE_URL`** for TomorrowOS ↔ Supabase.
 5. **Prefer `npx @tomorrowos/sdk init`** (or the package’s `templates/cms-starter`) as the project seed. Do not rebuild pairing, WebSocket, or playlist APIs from scratch.
 6. **Never commit secrets** into git. Put credentials only in Replit **Secrets** (and optionally mirror non-secret flags in `.env` that reference env vars).
-7. After Q&A, apply configuration, install deps, start the server, and verify:
-   - HTTP Control Panel loads
-   - `GET /brand.json` returns 200
-   - WebSocket upgrade on `wss://<repl-host>/` succeeds (critical for TV pairing)
+7. After Q&A, **configure and start** — do **not** run a long test suite (see **Post-Q&A: minimal verification only**).
 8. **Follow the Runtime & Replit publish rules below exactly.** A project that cannot Deploy / Publish on Replit is incomplete.
 
 **Question order after Q1:**
 
-- If **≤ 5 screens:** Q1 → Q3 → Q4 → execution checklist
-- If **> 5 screens:** Q1 → Q2 → Q3 → Q4 → execution checklist
+- If **≤ 5 screens:** Q1 → Q3 → (Q3b if Cloudinary) → Q4 → execution checklist
+- If **> 5 screens:** Q1 → Q2 → Q3 → (Q3b if Cloudinary) → Q4 → execution checklist
 
-Never insert extra questions between these steps.
+Never insert extra questions between these steps. **Never skip Question 3b** when the user chose Cloudinary.
 
 ---
 
@@ -200,7 +201,7 @@ Allowed extras (optional): `"build-player": "tomorrowos build --platform tizen"`
     "node": ">=20"
   },
   "dependencies": {
-    "@tomorrowos/sdk": "^0.7.9",
+    "@tomorrowos/sdk": "^0.8.0",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   },
@@ -252,21 +253,13 @@ If the workspace already has a `.replit`, **merge** these keys — do not wipe u
 
 ### Publish readiness checklist (before telling the user “done”)
 
-1. Replit project / primary artifact is **Web app** (not API-only / `api-kind`)
-2. `.replit` has `entrypoint = "server.ts"`, `modules = ["nodejs-20"]`, `[[ports]]` with `externalPort = 80`, `deploymentTarget = "autoscale"`
-3. Publishing type is **Autoscale** or **Reserved VM** (not Static-only)
-4. `package.json` has `scripts.start` = `tsx server.ts`
-5. `tsx` is listed under `dependencies` (runtime-safe for Deploy)
-6. Dependency is `@tomorrowos/sdk` (not a fork or vendored rewrite)
-7. `.replit` Run + `[deployment].run` use `npm run start`
-8. Node is **20+**
-9. Preview at `/` shows the TomorrowOS Control Panel (not Canvas, not another app, not API JSON)
-10. Stale processes / port conflicts cleared before publish
-11. `npm run start` prints `[TomorrowOS] listening on http://0.0.0.0:...`
-12. Browser WebSocket test to `wss://<host>/` succeeds
-13. Secrets required by the Q&A answers are set (`SUPABASE_URL`, Cloudinary, etc.)
-
-If any item fails, fix it before finishing.
+**Only these three checks matter after setup.** Do not add more unless Publish fails.
+
+1. **Web app, not API** — project / primary artifact is **Web app** (not `api-kind` / API-only).
+2. **`.replit` is correct** — `entrypoint = "server.ts"`, `modules = ["nodejs-20"]`, `[[ports]]` with `externalPort = 80`, `deploymentTarget = "autoscale"`, Run/Deploy = `npm run start`.
+3. **Preview at `/`** — after `npm run start`, logs show `[TomorrowOS] listening on http://0.0.0.0:...` and Preview shows the Control Panel (HTML), not empty / API JSON.
+
+If all three pass, tell the user setup is complete. **Do not** block on extra tests below.
 
 ### Preview requirements (Replit workspace)
 
@@ -300,11 +293,37 @@ Tell the user their live CMS URLs:
 
 Replace `YOUR-REPLIT-DOMAIN` with the actual published hostname (e.g. `my-cms.replit.app`).
 
-Verify after publish:
+**Do not** run post-publish smoke tests unless the user reports a problem. Telling them the URL is enough.
+
+---
+
+## Post-Q&A: minimal verification only
+
+After Questions 1–4, **configure → `npm install` → `npm run start` → done.**
+
+### Do (maximum)
+
+1. Confirm **Web app** artifact (not API) — **most important**.
+2. Write Secrets / `.env` / `brand.json` / `server.ts` / `.replit` from answers.
+3. `npm install` && `npm run start`.
+4. Glance at logs for `[TomorrowOS] listening on http://0.0.0.0:...`.
+5. Glance at Preview — Control Panel visible at `/`.
 
-1. `https://YOUR-REPLIT-DOMAIN/` shows the Control Panel (not empty, not API docs).
-2. `https://YOUR-REPLIT-DOMAIN/brand.json` returns 200.
-3. WebSocket to `wss://YOUR-REPLIT-DOMAIN/` succeeds.
+### Do NOT run after setup (unless user asks or Publish fails)
+
+- ❌ **Supabase connection test** (no `psql`, no DB ping, no “testing Supabase connection…”)
+- ❌ **Cloudinary upload test**
+- ❌ **`curl` / `fetch` on `/brand.json`** as a formal gate
+- ❌ **Browser WebSocket console snippet** as a formal gate
+- ❌ **Publishing dry-run** unless the user asked to publish now
+- ❌ **Long troubleshooting loops** when Preview already shows the Control Panel
+- ❌ Re-running the full **Publish readiness checklist** item-by-item in chat
+
+If Preview shows the Control Panel and the project is **Web app** type, **stop testing** and give the user their URL and next steps.
+
+### Only if Preview is empty or Publish fails
+
+Then (and only then) check: API vs Web type → `.replit` ports/`deploymentTarget` → stale process / port conflict → see **Failure recovery cheat sheet**.
 
 ---
 
@@ -383,6 +402,7 @@ DATABASE_SSL=true
 ```
 
 5. **Do not** write the real password into committed files.
+6. **Do not** test the Supabase connection after saving the Secret — configuration only.
 
 If the user refuses Supabase but chose > 5 screens, warn them SQLite on Replit is fragile for fleets, then offer SQLite only after they confirm.
 
@@ -402,20 +422,47 @@ If the user refuses Supabase but chose > 5 screens, warn them SQLite on Replit i
 >
 > Do you want me to set up **Cloudinary**? (yes / no)
 
-### If YES — Cloudinary
+### If YES — Cloudinary → go to Question 3b (do not ask Question 4 yet)
 
-**Ask for (or open a Secrets form for):**
+Choosing Cloudinary **does not finish** Question 3. Immediately continue to **Question 3b** below.
 
-- `CLOUDINARY_CLOUD_NAME`
-- `CLOUDINARY_API_KEY`
-- `CLOUDINARY_API_SECRET`
-- Optional: `CLOUDINARY_FOLDER` (e.g. `tomorrowos`)
+---
+
+## Question 3b — Cloudinary credentials (mandatory if Q3 = Cloudinary)
 
-Store these as Replit Secrets. The SDK auto-detects them and uploads media to Cloudinary instead of local disk.
+> **Ask this before Question 4.** Do not jump to `brand.json` until the user has provided credentials or confirmed they are saved as Replit Secrets.
+
+**Ask exactly (copy wording):**
+
+> Great — I’ll use **Cloudinary** for media uploads.
+>
+> Please paste your Cloudinary credentials (from [cloudinary.com/console](https://cloudinary.com/console) → Dashboard → **API Keys**). I will store them as Replit **Secrets** — never in committed files:
+>
+> 1. **`CLOUDINARY_CLOUD_NAME`** — your cloud name (e.g. `dxyz123abc`)
+> 2. **`CLOUDINARY_API_KEY`** — API Key
+> 3. **`CLOUDINARY_API_SECRET`** — API Secret
+>
+> Optional: **`CLOUDINARY_FOLDER`** (e.g. `tomorrowos`) — say if you want a folder prefix.
+>
+> You can paste all three in one reply, or use Replit’s Secrets panel and tell me when each Secret is set.
+
+**You must then:**
+
+1. Create / update Replit Secrets:
+   - `CLOUDINARY_CLOUD_NAME=<user value>`
+   - `CLOUDINARY_API_KEY=<user value>`
+   - `CLOUDINARY_API_SECRET=<user value>`
+   - Optional: `CLOUDINARY_FOLDER=<user value>`
+2. **Do not** write real secrets into `.env` files that are committed to git. Replit Secrets only (or `.env` that is gitignored and references env vars).
+3. **Do not** invent or placeholder Cloudinary credentials.
+4. **Do not** proceed to Question 4 until all three required Secrets exist.
+5. **Do not** run a Cloudinary upload test — configuration only.
 
 Tell the user:
 
-> After Cloudinary Secrets are set, restart the Repl. New uploads should return `https://res.cloudinary.com/...` URLs.
+> After Cloudinary Secrets are set, we’ll finish branding and start the CMS. New uploads will return `https://res.cloudinary.com/...` URLs.
+
+**If the user does not have a Cloudinary account yet:** tell them to sign up at cloudinary.com, create API keys, then return with the three values. **Wait** — do not skip to Question 4.
 
 ### If NO — Replit Object Storage (or local)
 
@@ -546,8 +593,6 @@ CLOUDINARY_API_SECRET=...
 
 ### E. Install and run
 
-**Before starting:** stop stale processes, clear old background tasks, free the port if needed, restart workspace if stuck.
-
 ```bash
 npm install
 npm run start
@@ -555,30 +600,15 @@ npm run start
 
 (Use `npm run dev` only for local edit/watch. **Publish / Deploy / Replit Run must use `npm run start`.**)
 
-Confirm logs contain something like:
-
-```text
-[TomorrowOS] listening on http://0.0.0.0:<PORT>
-```
-
-Confirm the **Web preview** (not Canvas) shows the Control Panel at `/`.
-
-### F. Verify before telling the user “done”
+**Minimal check:** logs contain `[TomorrowOS] listening on http://0.0.0.0:...` and Preview shows Control Panel at `/`. Then proceed to **G** — no further tests.
 
-1. Replit project type is **Web**; preview at `/` shows Control Panel (not empty, not Canvas-only).
-2. Open the Control Panel URL.
-3. `GET /brand.json` → 200 and correct `name` / colours.
-4. In browser console on the Control Panel origin:
+### F. Done — skip extended verification
 
-```javascript
-const ws = new WebSocket(location.origin.replace(/^http/, "ws") + "/");
-ws.onopen = () => console.log("WS OK");
-ws.onerror = (e) => console.log("WS ERR", e);
-```
+If the **three-item Publish readiness checklist** passes (especially **Web app, not API**), mark setup complete.
 
-5. Confirm the **Publish readiness checklist** in **Runtime & Replit publish rules**.
+**Do not** run WebSocket console tests, Supabase connection tests, or `brand.json` curl checks here.
 
-If WebSocket fails, fix Run command / process crash / sleep **before** asking the user to pair a TV.
+Only investigate further if Preview is empty, server crashed, or user reports Publish failure.
 
 ### G. Tell the user next steps (no code)
 
@@ -611,12 +641,14 @@ Do **not**:
 - Change the production start command away from `tsx server.ts` / `npm run start`
 - Point Supabase at Replit’s reserved `DATABASE_URL` when `SUPABASE_URL` should be used
 - Skip Cloudinary recommendation without stating the persistence tradeoff
+- **Skip Question 3b** after the user chooses Cloudinary — always collect `CLOUDINARY_*` Secrets before Question 4
 - Claim uploads are “permanent” on Replit local disk without Object Storage or Cloudinary
 - Leave `tsx` only in `devDependencies` if the Deploy pipeline installs production deps only
 - Use Canvas preview as the primary CMS verification surface
 - Serve a different app or API-only response at `/` instead of the Control Panel
 - Create the Repl as **API-only** or publish with **Static Deployment** only
 - Omit `[[ports]]` / `deploymentTarget` from `.replit` when setting up for Publish
+- Run **Supabase connection tests**, **WebSocket console tests**, or other post-setup smoke tests unless Preview fails or the user asks
 
 ---
 
@@ -657,6 +689,8 @@ TOMORROWOS_STORE=sqlite
 
 ## Protocol version
 
-`replit-setup/1.2` — aligned with TomorrowOS protocol `1.0` and `@tomorrowos/sdk` store drivers `sqlite` | `supabase` | `postgres` | `memory`.
+`replit-setup/1.4` — aligned with TomorrowOS protocol `1.0` and `@tomorrowos/sdk` store drivers `sqlite` | `supabase` | `postgres` | `memory`.
+
+**Changelog 1.4:** **Question 3b** — mandatory Cloudinary credential collection (Replit Secrets) before Question 4; fixes agents skipping secrets after “yes” to Cloudinary.
 
-**Changelog 1.2:** Web app deployability rules — avoid `api-kind` publish failure; full `.replit` with `[[ports]]`, `deploymentTarget = "autoscale"`, `entrypoint = "server.ts"`.
+**Changelog 1.3:** minimal post-Q&A verification — no Supabase/WS smoke tests; prioritize **Web app vs API** only.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tomorrowos/sdk",
-  "version": "0.7.9",
+  "version": "0.8.0",
   "description": "TomorrowOS CMS server SDK - WebSocket transport, pairing, device commands, optional static CMS UI. Includes CLI (tomorrowos init / build) and starter templates.",
   "type": "module",
   "main": "./dist/index.js",

package/templates/cms-starter/package.json

@@ -1,6 +1,6 @@
 {
   "name": "my-cms",
-  "version": "0.7.9",
+  "version": "0.8.0",
   "description": "CMS server on @tomorrowos/sdk. Add your UI (React, static files, etc.) alongside this server.",
   "private": true,
   "type": "module",
@@ -13,7 +13,7 @@
     "build-player": "tomorrowos build --platform tizen"
   },
   "dependencies": {
-    "@tomorrowos/sdk": "^0.7.9",
+    "@tomorrowos/sdk": "^0.8.0",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   },