@tomorrowos/sdk 0.9.34 → 0.9.40

package/REPLIT_SETUP.md

@@ -12,7 +12,8 @@ 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.
-Artifact kind must be **web** (never **api**). Question 3 only updates **brand.json**.
+Artifact kind must be **web** (never **api**). Collect SUPABASE_URL once only — never ask for the connection string twice.
+Question 3 branding fields are all optional; missing values keep starter brand.json defaults.
 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.
 ```
@@ -58,20 +59,23 @@ Replit Agent must ask **only** the questions defined in **this file**, in **this
 
 | Step | Section | When |
 |------|---------|------|
-| 1 | **Question 1** — Supabase connection string | Always |
+| 1 | **Question 1** — Supabase connection string (**once**) | Always |
 | 2 | **Question 2** — Media storage (+ Cloudinary Secrets if chosen) | Always (after Q1) |
-| 3 | **Question 3** — Brand / TomorrowOS app look | Always last, before execution |
+| 3 | **Question 3** — Brand / TomorrowOS app look (**all fields optional**) | Always last, before execution |
 
 **That is the complete list.** There are no other setup questions. **Do not** ask how many screens / devices. There is **no** “Question 2b” — Cloudinary credentials are collected **inside Question 2**, immediately after the user chooses Cloudinary.
 
+**Critical — Question 1 (Supabase) collected once only:** Asking for the Postgres connection string **is** selecting Supabase. Collect `SUPABASE_URL` in **one** step (Secrets UI **or** chat paste — not both). After it is saved, **never** ask for the connection string / `SUPABASE_URL` again (not in Q2, Q3, execution, Publish, or “confirm Secrets”).
+
 **Critical:** Question 2 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 3. Do **not** skip to branding with placeholder or invented credentials.
 
+**Critical — Question 3:** Every branding field is **optional**. Empty / skip / “use defaults” → keep values from the starter **`brand.json`**. Do **not** re-ask for missing name or colours.
 
-If the user volunteers extra info early (e.g. brand name before Q3), **record it** and still ask the current question’s required fields you do not yet have. Do not skip ahead to execution until Q1–Q3 are complete (Question 2 includes Cloudinary Secrets when applicable).
+If the user volunteers extra info early (e.g. brand name before Q3), **record it** and still ask the current question’s required fields you do not yet have. Do not skip ahead to execution until Q1–Q3 are complete (Question 2 includes Cloudinary Secrets when applicable). For Q3, “complete” includes the user skipping or leaving fields blank.
 
 If the user says “just set it up, don’t ask questions,” respond:
 
-> I need a few quick answers from REPLIT_SETUP.md (Supabase connection string, media storage — plus Cloudinary credentials if you choose Cloudinary — 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 (Supabase connection string once, media storage — plus Cloudinary credentials if you choose Cloudinary — and optional 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`.
 
@@ -83,6 +87,8 @@ Then ask **Question 1** — do not switch to `LLM_PROMPT.md`.
 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 2, **stay on Question 2** and immediately show the Secrets form — do **not** open a separate “2b” step or announce a new question number.
 3. **Do not invent** Cloudinary credentials, Supabase URLs, or brand colours. **Do not ask** screen / device count.
 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.
+4a. **Never collect `SUPABASE_URL` twice.** One Question 1 capture is enough for the whole wizard and execution checklist.
+4b. **Question 3 fields are all optional.** Missing values → keep starter `brand.json` defaults; do not block or re-prompt.
 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**).
@@ -372,26 +378,38 @@ Then (and only then) check: API vs Web type → `.replit` ports/`deploymentTarge
 
 ---
 
-## Question 1 — Supabase connection (always)
+## Question 1 — Supabase connection (always, **once**)
 
 > **This is the first setup question.** Always configure Supabase. **Do not** ask how many screens / devices.
 
+### Collect `SUPABASE_URL` exactly once (IRON RULE)
+
+Pasting / saving the connection string **is** choosing Supabase. Treat that as the full Question 1 answer.
+
+| Allowed (pick **one**) | Forbidden |
+|------------------------|-----------|
+| Open the Replit **Secrets** UI for `SUPABASE_URL` **or** ask the user to paste the string in chat | Asking “Do you want Supabase?” and then asking for the connection string again |
+| Save Secret once, then move on | Opening Secrets **and** also asking them to paste the same URI in chat |
+| Reuse the saved Secret in execution | Asking again in Q2 / Q3 / “confirm your Supabase Secret” / Publish / checklist |
+
+If `SUPABASE_URL` is **already** present in Replit Secrets when Question 1 starts, **do not** ask for it again — confirm you will use the existing Secret and proceed to Question 2 (unless the user explicitly wants to replace it).
+
 **Preferred on Replit:** open an **input / Secrets** UI where the user pastes the connection string into a field for:
 
 - `SUPABASE_URL`
 
-**Ask exactly (copy wording; do not substitute LLM_PROMPT questions):**
+**Only if** the Secrets UI is unavailable, ask exactly in chat (copy wording; do not substitute LLM_PROMPT questions). **Do not** also open a second Secrets prompt for the same value:
 
 > Paste your Supabase Postgres connection string below. I will store it as the Replit Secret **`SUPABASE_URL`** (not `DATABASE_URL` — that name is often reserved by Replit).
 >
 > Example shape: `postgresql://postgres.[PROJECT]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:6543/postgres`
 >
-> Also confirm whether SSL is required (usually **yes** for Supabase).
+> SSL is assumed **yes** for Supabase unless you say otherwise — you do not need to answer a separate SSL question if you already pasted the URI.
 
 **You must then:**
 
-1. Create / update Replit Secret: `SUPABASE_URL=<user value>`
-2. Create / update Replit Secret or `.env`:
+1. Create / update Replit Secret: `SUPABASE_URL=<user value>` (**once**).
+2. Create / update Replit Secret or `.env` flags only (not a second paste of the URI):
    - `TOMORROWOS_STORE=supabase`
    - `DATABASE_SSL=true` (unless the user explicitly says SSL is off)
 3. Update `server.ts` so the store uses Supabase via `SUPABASE_URL`:
@@ -421,17 +439,12 @@ tomorrowos.listen({
 });
 ```
 
-4. Ensure `.env` / Secrets include:
-
-```env
-TOMORROWOS_STORE=supabase
-SUPABASE_URL=postgresql://...
-DATABASE_SSL=true
-```
+4. Ensure `.env` / Secrets include `TOMORROWOS_STORE=supabase` and `DATABASE_SSL=true`. The connection string itself lives **only** in the Secret already saved in step 1 — **do not** ask the user to paste it into `.env` or chat again.
 
 5. **Do not** write the real password into committed files.
 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 1.
-7. **Do not** proceed to Question 2 until `SUPABASE_URL` is saved.
+7. **Do not** proceed to Question 2 until `SUPABASE_URL` is saved (or was already present and reused).
+8. **After Question 1 completes, never re-request `SUPABASE_URL`.** Execution checklist step B must **reuse** the existing Secret — wire env / `server.ts` silently.
 
 If the user refuses Supabase, warn that Replit fleets need a durable Postgres store, then offer SQLite only after they explicitly confirm.
 
@@ -499,35 +512,45 @@ The SDK auto-detects these env vars and uploads media to Cloudinary. New uploads
 
 ---
 
-## Question 3 — Brand / TomorrowOS app look (`brand.json` only)
+## Question 3 — Brand / TomorrowOS app look (`brand.json` only; **all fields optional**)
 
 > **Scope:** Question 3 answers **only** update **`brand.json`** — colours, name, tagline, logo path, etc. They configure how the **TomorrowOS player app** looks and metadata flags.
 >
 > **Question 3 does NOT affect:** Replit Publish, artifact `kind`, `.replit`, `server.ts`, Secrets, Supabase, Cloudinary, ports, deployment target, or CMS server wiring. **Never** change deploy/runtime config based on branding answers.
+>
+> **Every field below is optional.** The user may skip the whole question, answer only some fields, or say “use defaults”. For anything missing, **keep the existing starter `brand.json` values** (from `templates/cms-starter/brand.json` / project `brand.json` after `init`). **Do not** invent a second branding prompt. **Do not** block setup because name or colours were omitted.
 
 > **This is the only branding / platform / use-case question block.** Do not ask separate LLM_PROMPT “target platform”, “use case”, or “hosting” questions before this. **Do not** ask screen count.
 
-**Ask exactly (one message; user may answer in one reply):**
+**Ask exactly (one message; user may answer in one reply, partially, or skip):**
 
-> Let’s brand your TomorrowOS experience. Please provide:
+> Let’s brand your TomorrowOS experience (**all optional** — reply “skip” or leave blank to keep the starter `brand.json` defaults):
 >
-> 1. **Product / venue name** (shown on screens and the Control Panel)
-> 2. **Tagline** (optional)
-> 3. **Primary colour** (hex, e.g. `#FF8A3D`)
-> 4. **Background colour** (hex, optional — default `#FAFAF9`)
-> 5. **Text colour** (hex, optional — default `#0A0908`)
-> 6. **Secondary / accent colour** (hex, optional)
-> 7. **Logo** — upload an SVG/PNG into the project, or give a URL I can fetch into `./assets/`
+> 1. **Product / venue name** (optional — default from `brand.json`, e.g. `My Venue`)
+> 2. **Tagline** (optional — default e.g. `Digital signage`)
+> 3. **Primary colour** (optional hex — default e.g. `#FF8A3D`)
+> 4. **Background colour** (optional — default e.g. `#FAFAF9`)
+> 5. **Text colour** (optional — default e.g. `#0A0908`)
+> 6. **Secondary / accent colour** (optional — default e.g. `#F5F3EF`)
+> 7. **Logo** (optional) — upload an SVG/PNG, or a URL to fetch into `./assets/` (otherwise keep `./assets/logo.svg`)
+
+**Defaults rule (mandatory):**
 
+1. Start from the current project **`brand.json`** (after `init`, this matches the SDK starter).
+2. Overlay **only** fields the user actually provided.
+3. If the user gives **no** product name → keep existing `"name"`.
+4. If the user gives **no** colours → keep existing `primaryColor` / `backgroundColor` / `textColor` / `secondaryColor`.
+5. If the user says **skip** / **defaults** / **n/a** / sends an empty answer → leave `brand.json` unchanged (except set `cms.hostingTarget` to `"here"` if needed — see below).
+6. **Never** re-ask for missing branding fields. **Never** treat blank name/colour as an error.
 
-If the user only gives a name and primary colour, use defaults for the rest and say what you assumed.
+**Then write / update `brand.json` only** at the project root (validate mentally against `brand.schema.json` in the SDK). **Do not** modify `.replit`, `server.ts`, Secrets, or deployment settings from these answers.
 
-**Then write / update `brand.json` only** at the project root (validate mentally against `brand.schema.json` in the SDK). **Do not** modify `.replit`, `server.ts`, Secrets, or deployment settings from these answers. Minimum example:
+Example when the user provided only a name (other fields kept from starter):
 
 ```json
 {
-  "name": "<user name>",
-  "tagline": "<user tagline or Digital signage>",
+  "name": "<user name or keep starter name>",
+  "tagline": "Digital signage",
   "targetPlatforms": ["tizen"],
   "primaryColor": "#FF8A3D",
   "secondaryColor": "#F5F3EF",
@@ -575,14 +598,17 @@ If `init` is inappropriate (existing customised project), merge carefully:
 
 ### B. Apply store + media Secrets
 
-**Supabase (always from Question 1):**
+**Supabase (always from Question 1 — reuse; do not ask again):**
+
+Use the **`SUPABASE_URL` already saved** in Question 1. Wire flags only:
 
 ```env
 TOMORROWOS_STORE=supabase
-SUPABASE_URL=...
 DATABASE_SSL=true
 ```
 
+**Do not** prompt the user to paste the Postgres connection string a second time. **Do not** open another Secrets form for `SUPABASE_URL` unless the Secret is missing (should not happen if Q1 completed).
+
 **Cloudinary (if chosen):**
 
 ```env
@@ -659,6 +685,7 @@ Do **not**:
 - Replace `@tomorrowos/sdk` with a hand-rolled server
 - 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
+- **Ask for `SUPABASE_URL` / the Postgres connection string more than once** (Secrets UI + chat, or again during execution / Publish)
 - Skip Cloudinary recommendation without stating the persistence tradeoff
 - **Skip Cloudinary Secrets** after the user chooses Cloudinary — always collect `CLOUDINARY_*` inside Question 2 before Question 3
 - **Announce “Question 2b”** or a separate follow-up question — show the Secrets form immediately instead
@@ -669,6 +696,8 @@ Do **not**:
 - Create the Repl as **API-only** or publish with **Static Deployment** only
 - Set or leave artifact **`kind = "api"`** for the TomorrowOS CMS
 - Change `.replit`, `server.ts`, Secrets, or deployment config based on **Question 3** branding answers (those go in **`brand.json` only**)
+- **Require** product name, colours, or logo in Question 3 — all branding fields are optional; missing → starter `brand.json` defaults
+- **Re-ask** Question 3 for blank name/colour instead of keeping defaults
 - 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
@@ -712,7 +741,9 @@ TOMORROWOS_STORE=sqlite
 
 ## Protocol version
 
-`replit-setup/1.8` — aligned with TomorrowOS protocol `1.0` and `@tomorrowos/sdk` store drivers `sqlite` | `supabase` | `postgres` | `memory`.
+`replit-setup/1.9` — aligned with TomorrowOS protocol `1.0` and `@tomorrowos/sdk` store drivers `sqlite` | `supabase` | `postgres` | `memory`.
+
+**Changelog 1.9:** Question 1 collects `SUPABASE_URL` **once only** (no second Secrets/chat prompt in execution). Question 3 branding fields are **all optional**; missing values keep starter `brand.json` defaults.
 
 **Changelog 1.8:** Question 1 is always Supabase connection string (input / Secret). Removed screen-count branching (≤5 SQLite vs >5 Supabase). Media storage is Question 2; branding is Question 3.
 

package/VERCEL_QUESTIONS.md

@@ -1,6 +1,6 @@
 # Vercel / v0 — Verbatim question bank
 
-> **Protocol:** `vercel-questions/1.0` (pairs with `VERCEL_SETUP.md` 1.9+ / `@tomorrowos/sdk` 0.9.34+)  
+> **Protocol:** `vercel-questions/1.0` (pairs with `VERCEL_SETUP.md` 1.9+ / `@tomorrowos/sdk` 0.9.40+)  
 > **For Agents:** When asking the user a setup question, **copy-paste the block below for that step EXACTLY**.  
 > Do **not** paraphrase, reorder, rename options, or invent alternatives (no S3, no Supabase Storage, no “Blob recommended”, no “disable media”).  
 > After each answer, configure per `VERCEL_SETUP.md`, then paste the **next** block.

package/VERCEL_SETUP.md

@@ -5,7 +5,7 @@
 >
 > **On Vercel, this file is the setup questionnaire** (not `REPLIT_SETUP.md`, not `LLM_PROMPT.md`).
 >
-> Protocol id: `vercel-setup/1.9` — pairs with `@tomorrowos/sdk` **0.9.34+** (`templates/cms-starter-v0`, Fluid Functions WebSockets).
+> Protocol id: `vercel-setup/1.9` — pairs with `@tomorrowos/sdk` **0.9.40+** (`templates/cms-starter-v0`, Fluid Functions WebSockets).
 >
 > **Questions source of truth:** `VERCEL_QUESTIONS.md` — Agents must **open that file and paste each Q block verbatim**. Do not paraphrase.  
 > **Copy questions verbatim from `VERCEL_QUESTIONS.md`.** Do not invent alternate Q2 options (no “Supabase Storage”, no S3, no “disable media”, no making Blob the recommended option).  

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tomorrowos/sdk",
-  "version": "0.9.34",
+  "version": "0.9.40",
   "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",
@@ -20,6 +20,7 @@
     "README.md",
     "LLM_PROMPT.md",
     "REPLIT_SETUP.md",
+    "LOVABLE_SETUP.md",
     "VERCEL_SETUP.md",
     "VERCEL_QUESTIONS.md",
     "REPLIT_UPGRADE.md",