@tomorrowos/sdk 0.8.0 → 0.8.2

package/REPLIT_SETUP.md

@@ -12,7 +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.
+After all setup questions are answered (including Cloudinary Secrets if you chose Cloudinary), configure and start — minimal verification only (Web app type + Preview at /). **Never test Supabase connection** — save `SUPABASE_URL` and move on. No Supabase or WebSocket tests.
 Do not skip steps.
 ```
 
@@ -35,16 +35,15 @@ 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** |
+| 3 | **Question 3** — Media storage (+ Cloudinary Secrets if chosen) | Always (after Q1 or Q2) |
 | 4 | **Question 4** — Brand / TomorrowOS app look | Always last, before execution |
 
-**That is the complete list.** There are no other setup questions.
+**That is the complete list.** There are no other setup questions. There is **no** “Question 3b” — Cloudinary credentials are collected **inside Question 3**, immediately after the user chooses Cloudinary.
 
-**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.
+**Critical:** Question 3 is **not complete** when the user says “Cloudinary” or “yes”. You **must** immediately show the Cloudinary Secrets input (same step — do **not** label a new question) and collect `CLOUDINARY_CLOUD_NAME`, `CLOUDINARY_API_KEY`, and `CLOUDINARY_API_SECRET` **before** 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, Q3b, Q4 if ≤5 screens and Cloudinary) 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 are complete (Question 3 includes Cloudinary Secrets when applicable).
 
 If the user says “just set it up, don’t ask questions,” respond:
 
@@ -56,21 +55,22 @@ Then ask **Question 1** — do not switch to `LLM_PROMPT.md`.
 
 ## Hard rules
 
-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.
+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). **Exception:** If the user chooses Cloudinary in Question 3, **stay on Question 3** and immediately show the Secrets form — do **not** open a separate “3b” step or announce a new question number.
 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, **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.
+9. **Supabase: configure only — never test.** Save `SUPABASE_URL` + `TOMORROWOS_STORE=supabase` and proceed. **Do not** ping Postgres, run `psql`, start the server solely to verify DB connectivity, or treat log errors like `ENOTFOUND` / `database connection failure` in **Replit dev / Preview** as a failed setup. Supabase often works only after **Publish** (production networking), not in the dev shell.
 
 **Question order after Q1:**
 
-- If **≤ 5 screens:** Q1 → Q3 → (Q3b if Cloudinary) → Q4 → execution checklist
-- If **> 5 screens:** Q1 → Q2 → Q3 → (Q3b if Cloudinary) → Q4 → execution checklist
+- If **≤ 5 screens:** Q1 → Q3 → Q4 → execution checklist
+- If **> 5 screens:** Q1 → Q2 → Q3 → Q4 → execution checklist
 
-Never insert extra questions between these steps. **Never skip Question 3b** when the user chose Cloudinary.
+Never insert extra questions between these steps. When the user chooses Cloudinary, **Question 3 continues** with the Secrets form immediately — then proceed to Q4 only after secrets are saved.
 
 ---
 
@@ -201,7 +201,7 @@ Allowed extras (optional): `"build-player": "tomorrowos build --platform tizen"`
     "node": ">=20"
   },
   "dependencies": {
-    "@tomorrowos/sdk": "^0.8.0",
+    "@tomorrowos/sdk": "^0.8.2",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   },
@@ -301,6 +301,22 @@ Replace `YOUR-REPLIT-DOMAIN` with the actual published hostname (e.g. `my-cms.re
 
 After Questions 1–4, **configure → `npm install` → `npm run start` → done.**
 
+### Supabase: never test in Replit dev (mandatory)
+
+When the user chose Supabase (>5 screens), setup is **save credentials + wire `server.ts` + start** — **nothing else**.
+
+**Forbidden after Q&A (and after Question 2):**
+
+- ❌ “Testing Supabase connection…”
+- ❌ `psql`, `pg`, Prisma `db pull`, or any one-off DB probe script
+- ❌ Restarting / debugging the server **because** logs show `database connection failure`, `getaddrinfo ENOTFOUND`, or `db.*.supabase.co can't be resolved`
+- ❌ Telling the user their Supabase URL is wrong **only** because dev Preview cannot resolve the host
+- ❌ Blocking setup completion on Supabase connectivity
+
+**Expected in Replit dev:** Supabase host may **not resolve** in the dev environment. That is **normal**. The Control Panel at `/` can still load. Mark setup **complete** when Web app type is correct and Preview shows the Control Panel — **even if** Supabase errors appear in logs.
+
+**When Supabase actually gets validated:** after the user **Publishes** the Repl and uses the live URL — not during the setup wizard.
+
 ### Do (maximum)
 
 1. Confirm **Web app** artifact (not API) — **most important**.
@@ -311,7 +327,7 @@ After Questions 1–4, **configure → `npm install` → `npm run start` → don
 
 ### Do NOT run after setup (unless user asks or Publish fails)
 
-- ❌ **Supabase connection test** (no `psql`, no DB ping, no “testing Supabase connection…”)
+- ❌ **Supabase connection test** — **never**, including after `npm run start` (no `psql`, no DB ping, no “verifying database…”, no retry loops for `ENOTFOUND`)
 - ❌ **Cloudinary upload test**
 - ❌ **`curl` / `fetch` on `/brand.json`** as a formal gate
 - ❌ **Browser WebSocket console snippet** as a formal gate
@@ -319,7 +335,7 @@ After Questions 1–4, **configure → `npm install` → `npm run start` → don
 - ❌ **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.
+If Preview shows the Control Panel and the project is **Web app** type, **stop testing** and give the user their URL and next steps — **even when using Supabase and dev logs show DB connection errors**.
 
 ### Only if Preview is empty or Publish fails
 
@@ -402,7 +418,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.
+6. **Do not** test the Supabase connection after saving the Secret — **configuration only**. No probe, no `npm run start` just to verify DB, no fixing “connection failure” in dev. Saving `SUPABASE_URL` completes Question 2.
 
 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.
 
@@ -410,6 +426,8 @@ If the user refuses Supabase but chose > 5 screens, warn them SQLite on Replit i
 
 ## Question 3 — Media storage (uploads / thumbnails)
 
+### Step A — Ask storage choice
+
 **Ask exactly:**
 
 > How should playlist media (images/videos) be stored?
@@ -422,47 +440,38 @@ 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 → go to Question 3b (do not ask Question 4 yet)
+### Step B — If YES / Cloudinary (same Question 3 — no “3b”, no extra question)
 
-Choosing Cloudinary **does not finish** Question 3. Immediately continue to **Question 3b** below.
+**Do this immediately** when the user chooses Cloudinary. **Do not** say “Question 3b”, “next step”, or “Great — I’ll use Cloudinary” as a separate message before the form. **Go straight to the Secrets input.**
 
----
-
-## Question 3b — Cloudinary credentials (mandatory if Q3 = Cloudinary)
+**Preferred on Replit:** open the **Replit Secrets** UI with fields for:
 
-> **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.
+- `CLOUDINARY_CLOUD_NAME`
+- `CLOUDINARY_API_KEY`
+- `CLOUDINARY_API_SECRET`
+- Optional: `CLOUDINARY_FOLDER` (e.g. `tomorrowos`)
 
-**Ask exactly (copy wording):**
+**If Secrets UI is unavailable, ask exactly (one message with all fields):**
 
-> 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
+> Paste your Cloudinary credentials (from [cloudinary.com/console](https://cloudinary.com/console) → Dashboard → **API Keys**). I will store them as Replit **Secrets**:
 >
-> Optional: **`CLOUDINARY_FOLDER`** (e.g. `tomorrowos`) — say if you want a folder prefix.
+> 1. **`CLOUDINARY_CLOUD_NAME`**
+> 2. **`CLOUDINARY_API_KEY`**
+> 3. **`CLOUDINARY_API_SECRET`**
 >
-> You can paste all three in one reply, or use Replit’s Secrets panel and tell me when each Secret is set.
+> Optional: **`CLOUDINARY_FOLDER`**
 
 **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.
+1. Save Replit Secrets: `CLOUDINARY_CLOUD_NAME`, `CLOUDINARY_API_KEY`, `CLOUDINARY_API_SECRET` (and optional `CLOUDINARY_FOLDER`).
+2. **Do not** write real secrets into committed files.
+3. **Do not** invent or placeholder 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:
+**If the user does not have a Cloudinary account yet:** tell them to sign up at cloudinary.com and return with API keys. **Wait** on Question 3 — do not skip to Question 4.
 
-> 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.
+The SDK auto-detects these env vars and uploads media to Cloudinary. New uploads will return `https://res.cloudinary.com/...` URLs.
 
 ### If NO — Replit Object Storage (or local)
 
@@ -600,13 +609,13 @@ npm run start
 
 (Use `npm run dev` only for local edit/watch. **Publish / Deploy / Replit Run must use `npm run start`.**)
 
-**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.
+**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. **Ignore** Supabase `ENOTFOUND` / `database connection failure` in dev logs; do not debug DB for that reason alone.
 
 ### F. Done — skip extended verification
 
 If the **three-item Publish readiness checklist** passes (especially **Web app, not API**), mark setup complete.
 
-**Do not** run WebSocket console tests, Supabase connection tests, or `brand.json` curl checks here.
+**Do not** run WebSocket console tests, Supabase connection tests, or `brand.json` curl checks here. **Supabase `ENOTFOUND` in dev is not a setup failure** — tell the user DB will connect after Publish if needed.
 
 Only investigate further if Preview is empty, server crashed, or user reports Publish failure.
 
@@ -641,7 +650,8 @@ 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
+- **Skip Cloudinary Secrets** after the user chooses Cloudinary — always collect `CLOUDINARY_*` inside Question 3 before Question 4
+- **Announce “Question 3b”** or a separate follow-up question — show the Secrets form immediately instead
 - 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
@@ -649,6 +659,7 @@ Do **not**:
 - 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
+- **Debug or “fix” Supabase** because dev logs show `getaddrinfo ENOTFOUND` or `database connection failure` — save config and finish setup instead
 
 ---
 
@@ -682,15 +693,20 @@ TOMORROWOS_STORE=sqlite
 | `EADDRINUSE` on start | Old process holding port | Stop stale processes, clear background tasks, restart Repl |
 | Upload: `storage.objects.create` denied | Replit Object Storage IAM | Fix Object Storage permissions **or** switch to Cloudinary |
 | Upload OK then thumbnails vanish later | Non-persistent `public/uploads` | Object Storage or Cloudinary |
-| Supabase connection errors | Wrong URL or using reserved `DATABASE_URL` | Use `SUPABASE_URL` + `TOMORROWOS_STORE=supabase` |
+| Supabase `ENOTFOUND` / `can't be resolved` in **dev** logs after setup | Replit dev network cannot reach Supabase host | **Not a setup failure.** Finish wizard; user validates DB after **Publish** |
+| Supabase connection errors on **published** URL | Wrong URL or using reserved `DATABASE_URL` | Use `SUPABASE_URL` + `TOMORROWOS_STORE=supabase`; pooler URL `*.pooler.supabase.com:6543` |
 | Pairing works on one Repl but not another | That Repl’s WS/backend only | Compare Run command and logs with a known-good Repl |
 
 ---
 
 ## Protocol version
 
-`replit-setup/1.4` — aligned with TomorrowOS protocol `1.0` and `@tomorrowos/sdk` store drivers `sqlite` | `supabase` | `postgres` | `memory`.
+`replit-setup/1.6` — aligned with TomorrowOS protocol `1.0` and `@tomorrowos/sdk` store drivers `sqlite` | `supabase` | `postgres` | `memory`.
+
+**Changelog 1.6:** **Never test Supabase** in Replit dev — `ENOTFOUND` / connection errors in Preview logs are expected; setup completes when Control Panel loads.
+
+**Changelog 1.5:** Cloudinary Secrets collected **inside Question 3** — no separate “3b” step; show Secrets form immediately when user picks Cloudinary.
 
-**Changelog 1.4:** **Question 3b** — mandatory Cloudinary credential collection (Replit Secrets) before Question 4; fixes agents skipping secrets after “yes” to Cloudinary.
+**Changelog 1.4:** mandatory Cloudinary credential collection before Question 4 (superseded by 1.5 flow).
 
 **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.8.0",
+  "version": "0.8.2",
   "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.8.0",
+  "version": "0.8.2",
   "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.8.0",
+    "@tomorrowos/sdk": "^0.8.2",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   },