@tomorrowos/sdk 0.9.40 → 0.9.41

package/VERCEL_SETUP.md

@@ -5,11 +5,11 @@
 >
 > **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.40+** (`templates/cms-starter-v0`, Fluid Functions WebSockets).
+> Protocol id: `vercel-setup/1.9` �?pairs with `@tomorrowos/sdk` **0.9.41+** (`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).  
-> **`TOMORROWOS_STORE` and `DATABASE_SSL` are agent-only** — set them automatically after Q1; never put them in a user-facing Env form for the customer to type.
+> **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).  
+> **`TOMORROWOS_STORE` and `DATABASE_SSL` are agent-only** �?set them automatically after Q1; never put them in a user-facing Env form for the customer to type.
 
 ## NON-NEGOTIABLE VERCEL RUNTIME CONTRACT
 
@@ -18,7 +18,7 @@ The following rules are **mandatory acceptance criteria**, not suggestions. The
 1. **One TomorrowOS instance only.** Use the shared instance exported through `api/index.ts`. **Never create a second `TomorrowOS` instance in `api/ws.ts`** or any other route.
 2. **Never use `public/` as the Vercel Output Directory.** The dashboard Output Directory must be **empty / unset**. Serve the Control Panel at runtime from `cms-panel/` through TomorrowOS `staticRoot`.
 3. **Preview may use Next only as an isolated reverse-proxy shell under `preview/`.** Preview must not replace TomorrowOS or determine the Production runtime.
-4. **Publish must use the Fluid Function.** Production must run `api/index.ts` → the shared exported `http.Server`, with Fluid compute enabled. It must not use `next start`, a static export, or a bare `(req, res)` handler.
+4. **Publish must use the Fluid Function.** Production must run `api/index.ts` �?the shared exported `http.Server`, with Fluid compute enabled. It must not use `next start`, a static export, or a bare `(req, res)` handler.
 5. **After every Production deployment, verify all three gates before saying setup is complete:**
    - `GET /status` returns TomorrowOS **JSON**, not HTML.
    - `GET /` returns the TomorrowOS **Control Panel**.
@@ -35,16 +35,16 @@ When a human pastes a prompt like this, **read this file and start Question 1 im
 ```text
 Follow @tomorrowos/sdk VERCEL_SETUP.md and set up my TomorrowOS CMS.
 First open VERCEL_QUESTIONS.md. For Q1, Q2, Q3: paste each question block VERBATIM (character-for-character). Do not rephrase options.
-Q2 must show Cloudinary (recommended) as option 1 — never Blob-as-recommended, never S3, never Supabase Storage.
-After database choice, YOU set TOMORROWOS_STORE and DATABASE_SSL — do not ask me to fill those.
+Q2 must show Cloudinary (recommended) as option 1 �?never Blob-as-recommended, never S3, never Supabase Storage.
+After database choice, YOU set TOMORROWOS_STORE and DATABASE_SSL �?do not ask me to fill those.
 Do not use LLM_PROMPT.md or REPLIT_SETUP.md. No OpenAI/LLM API keys.
 Apply the NON-NEGOTIABLE VERCEL RUNTIME CONTRACT exactly: one TomorrowOS instance; no public/ Output Directory; Preview Next only under preview/; Publish through the Fluid Function; verify /status JSON, / Control Panel, and WebSocket 101; pair devices only with the Production URL.
 ```
 
 Alternate triggers:
 
-- “Set up TomorrowOS on Vercel using VERCEL_SETUP.md”
-- “Configure my TomorrowOS CMS (Vercel wizard)”
+- “Set up TomorrowOS on Vercel using VERCEL_SETUP.md�?
+- “Configure my TomorrowOS CMS (Vercel wizard)�?
 
 When any of these fire, **ignore `REPLIT_SETUP.md` and `LLM_PROMPT.md`** for the Q&A phase (you may skim Replit docs only for shared SDK semantics).
 
@@ -57,9 +57,9 @@ When any of these fire, **ignore `REPLIT_SETUP.md` and `LLM_PROMPT.md`** for the
 TomorrowOS CMS is **one Node process** that serves:
 
 - Browser Control Panel at `GET /` (`public/` via `staticRoot`)
-- Device **WebSocket** on the same origin (`https` → players use `wss`)
+- Device **WebSocket** on the same origin (`https` �?players use `wss`)
 
-### Production / Publish — Node only (no Next.js)
+### Production / Publish �?Node only (no Next.js)
 
 | Required | Forbidden |
 |----------|-----------|
@@ -68,12 +68,12 @@ TomorrowOS CMS is **one Node process** that serves:
 | **Fluid compute** enabled (needed for WebSockets on Vercel) | Classic short-lived serverless with no WebSocket / no Fluid |
 | Durable store = **Postgres** (Supabase or Neon, pooled URL) | **SQLite / `data/*.db` as production store** on Vercel (ephemeral filesystem) |
 | Media = **Cloudinary** or **Vercel Blob** (durable HTTPS URLs) | Relying on local `public/uploads` alone for production fleets |
-| Env vars in **Vercel Project → Settings → Environment Variables** | Committing passwords / API secrets / `.env` with secrets |
+| Env vars in **Vercel Project �?Settings �?Environment Variables** | Committing passwords / API secrets / `.env` with secrets |
 | `cms.hostingTarget`: `"vercel"` in `brand.json` | Creating `.replit` / Replit artifact files |
 
 **Publish / Production Deploy** must run **`TomorrowOS.listen(...)`** directly. Do **not** put Next.js in front of Production traffic.
 
-### Publish `404: NOT_FOUND` — mandatory prevention (read before every deploy)
+### Publish `404: NOT_FOUND` �?mandatory prevention (read before every deploy)
 
 The production URL showing:
 
@@ -86,7 +86,7 @@ almost always means **Vercel still thinks this is a Next.js / static deploy**, n
 
 **Before every Production deploy, you MUST verify all of the following:**
 
-1. **Project → Settings → General → Framework Preset = Other** (or unset / null).  
+1. **Project �?Settings �?General �?Framework Preset = Other** (or unset / null).  
    If it still says **Next.js**, patch it via Vercel API / CLI / dashboard **before** redeploying.  
    `"framework": null` in `vercel.json` alone is **not enough** if the dashboard still says Next.js.
 2. **Install Command** = `npm install` / `pnpm install` / `yarn` (normal install).
@@ -101,7 +101,7 @@ almost always means **Vercel still thinks this is a Next.js / static deploy**, n
 
 **Setup is NOT complete** while Production `GET /` returns `404: NOT_FOUND` or WebSocket upgrade returns 200 HTML.
 
-### Publish static trap — `public/` served without Node (read this)
+### Publish static trap �?`public/` served without Node (read this)
 
 A common **worse** failure mode than `404: NOT_FOUND`:
 
@@ -110,7 +110,7 @@ A common **worse** failure mode than `404: NOT_FOUND`:
 - The panel shows **CMS unreachable** and console:  
   `Unexpected token 'T', "The page c"... is not valid JSON`
 
-**Root cause:** Vercel deployed `public/` as a **static site** (Output Directory = `public` or Framework=Other default *“public if it exists”*). **No Function** is running TomorrowOS.
+**Root cause:** Vercel deployed `public/` as a **static site** (Output Directory = `public` or Framework=Other default *“public if it exists�?). **No Function** is running TomorrowOS.
 
 **Fix (Scheme A):** use `cms-panel/` (not `public/`), Fluid Function `api/index.ts` + rewrites, Output Directory empty. Static UI is served **at runtime** via `staticRoot` in `listen()`.
 
@@ -124,7 +124,7 @@ curl -s https://YOUR-PROJECT.vercel.app/status | head -c 80
 
 **Setup is NOT complete** while `/status` returns HTML, the panel shows the JSON parse error, or devices cannot open `wss://`.
 
-### Preview (v0 / Vercel Agent sandbox) — Next.js shell allowed
+### Preview (v0 / Vercel Agent sandbox) �?Next.js shell allowed
 
 v0 Preview is often a **Next.js runtime** hardwired to `next dev`. A raw `tsx server.ts` may listen successfully while Preview still shows a blank page, because the sandbox intercepts the public port with Next before requests reach TomorrowOS.
 
@@ -134,10 +134,10 @@ v0 Preview is often a **Next.js runtime** hardwired to `next dev`. A raw `tsx se
 |---------------------|--------|
 | Next.js remains the Preview host | Satisfies v0 / sandbox expectations |
 | TomorrowOS on internal port | e.g. `TOMORROWOS_INTERNAL_PORT=3001` (not the public Preview port) |
-| Transparent HTTP reverse proxy | Next route/middleware forwards `/` (and Control Panel paths) → `http://127.0.0.1:3001` |
+| Transparent HTTP reverse proxy | Next route/middleware forwards `/` (and Control Panel paths) �?`http://127.0.0.1:3001` |
 | Start both processes in Preview | Next + `tsx server.ts` (or a `dev:preview` script that starts both) |
 
-**Preview WebSocket note:** HTTP proxy is enough for Control Panel HTML/API smoke checks. Device `wss` pairing may not work through a Next proxy in Preview — that is acceptable. **Pair devices against the Production Publish URL**, not v0 Preview.
+**Preview WebSocket note:** HTTP proxy is enough for Control Panel HTML/API smoke checks. Device `wss` pairing may not work through a Next proxy in Preview �?that is acceptable. **Pair devices against the Production Publish URL**, not v0 Preview.
 
 **Do not** replace TomorrowOS with a Next-only CMS. Next is a **Preview adapter**, not the product.
 
@@ -145,43 +145,43 @@ v0 Preview is often a **Next.js runtime** hardwired to `next dev`. A raw `tsx se
 
 ## Questionnaire scope (STRICT)
 
-Ask **only** these questions, in **this exact order**. **Copy the “Ask exactly” blocks verbatim** — do not paraphrase options.
+Ask **only** these questions, in **this exact order**. **Copy the “Ask exactly�?blocks verbatim** �?do not paraphrase options.
 
 | Step | Section | When |
 |------|---------|------|
-| 1 | **Question 1** — Database (Supabase → Neon → SQLite) | Always |
-| 2 | **Question 2** — Media (**Cloudinary recommended** → Vercel Blob → local) | Always (after Q1) |
-| 3 | **Question 3** — Brand / TomorrowOS look (`brand.json` only) | Always last |
+| 1 | **Question 1** �?Database (Supabase �?Neon �?SQLite) | Always |
+| 2 | **Question 2** �?Media (**Cloudinary recommended** �?Vercel Blob �?local) | Always (after Q1) |
+| 3 | **Question 3** �?Brand / TomorrowOS look (`brand.json` only) | Always last |
 
 **That is the complete list.** Do **not** ask how many screens / devices.
 
 **Forbidden invented Question 2 options (never offer these in chat or UI):**
 
-- ❌ “Vercel Blob **(recommended)**” as option 1 — Blob is option **2**, not recommended over Cloudinary
-- ❌ “Supabase Storage” / S3 bucket / `SUPABASE_SERVICE_ROLE_KEY` for media
-- ❌ “No media storage” / “disable media uploads” / “remote URLs only” as a numbered choice
-- ❌ Any media list that does not start with **Cloudinary (recommended)**
+- �?“Vercel Blob **(recommended)**�?as option 1 �?Blob is option **2**, not recommended over Cloudinary
+- �?“Supabase Storage�?/ S3 bucket / `SUPABASE_SERVICE_ROLE_KEY` for media
+- �?“No media storage�?/ “disable media uploads�?/ “remote URLs only�?as a numbered choice
+- �?Any media list that does not start with **Cloudinary (recommended)**
 
 **Forbidden Env UX after Question 1:**
 
-- ❌ Showing the user empty fields for `TOMORROWOS_STORE` or `DATABASE_SSL` to fill
-- ❌ Asking in chat “what should TOMORROWOS_STORE be?”
-- ✅ After DB choice + URL paste: **you** write those two vars silently (see Q1 Steps B/C/D)
+- �?Showing the user empty fields for `TOMORROWOS_STORE` or `DATABASE_SSL` to fill
+- �?Asking in chat “what should TOMORROWOS_STORE be?�?
+- �?After DB choice + URL paste: **you** write those two vars silently (see Q1 Steps B/C/D)
 
 **Forbidden extra questions (never ask, even if the user skips a step):**
 
-- ❌ OpenAI / Anthropic / Gemini / any LLM API key (`sk-…`, etc.)
-- ❌ “AI pairing”, “AI feature logic”, or inventing auth that needs an LLM key
-- ❌ Asking the user to type `TOMORROWOS_STORE` or `DATABASE_SSL`
-- ❌ Any secret not listed in Questions 1–3 (DB URL, media credentials, brand)
+- �?OpenAI / Anthropic / Gemini / any LLM API key (`sk-…`, etc.)
+- �?“AI pairing�? “AI feature logic�? or inventing auth that needs an LLM key
+- �?Asking the user to type `TOMORROWOS_STORE` or `DATABASE_SSL`
+- �?Any secret not listed in Questions 1�? (DB URL, media credentials, brand)
 
 TomorrowOS pairing and Control Panel logic live in `@tomorrowos/sdk`. They do **not** call OpenAI.
 
-If the user **skips** a Question 2 option, do **not** invent a substitute question. Re-state Question 2 choices **verbatim**, or proceed with local uploads + warning — never pivot to LLM keys or Supabase Storage.
+If the user **skips** a Question 2 option, do **not** invent a substitute question. Re-state Question 2 choices **verbatim**, or proceed with local uploads + warning �?never pivot to LLM keys or Supabase Storage.
 
-If the user says “just set it up, don’t ask questions,” respond:
+If the user says “just set it up, don’t ask questions,�?respond:
 
-> I need a few quick answers from VERCEL_SETUP.md (database — Supabase or Neon preferred — media storage with Cloudinary recommended, and branding). It takes about a minute and ensures the CMS works on Vercel.
+> I need a few quick answers from VERCEL_SETUP.md (database �?Supabase or Neon preferred �?media storage with Cloudinary recommended, and branding). It takes about a minute and ensures the CMS works on Vercel.
 
 Then ask **Question 1**.
 
@@ -189,10 +189,10 @@ Then ask **Question 1**.
 
 ## Hard rules
 
-1. **Open `VERCEL_QUESTIONS.md` first.** Paste Q1 → configure → paste Q2 → configure → paste Q3. Never paraphrase question options. Never use `LLM_PROMPT.md` or `REPLIT_SETUP.md` as the questionnaire. **Never** ask for OpenAI or other LLM API keys.
+1. **Open `VERCEL_QUESTIONS.md` first.** Paste Q1 �?configure �?paste Q2 �?configure �?paste Q3. Never paraphrase question options. Never use `LLM_PROMPT.md` or `REPLIT_SETUP.md` as the questionnaire. **Never** ask for OpenAI or other LLM API keys.
 2. **Question 2 options are fixed:** (1) Cloudinary **(recommended)**, (2) Vercel Blob, (3) local disk. Do not reorder; do not invent Supabase Storage / disable-uploads.
 3. **Cloudinary:** open **one** Vercel Env popup with **all** Cloudinary fields together. Do **not** quiz one credential at a time.
-4. **`TOMORROWOS_STORE` + `DATABASE_SSL` = agent-owned.** After Q1 choice (and URL if needed), set them yourself in Vercel Env Vars. **Never** include them as blank fields for the customer. Mapping: Supabase → `TOMORROWOS_STORE=supabase` + `DATABASE_SSL=true`; Neon → `TOMORROWOS_STORE=postgres` + `DATABASE_SSL=true`; SQLite → `TOMORROWOS_STORE=sqlite` (no `DATABASE_SSL` required).
+4. **`TOMORROWOS_STORE` + `DATABASE_SSL` = agent-owned.** After Q1 choice (and URL if needed), set them yourself in Vercel Env Vars. **Never** include them as blank fields for the customer. Mapping: Supabase �?`TOMORROWOS_STORE=supabase` + `DATABASE_SSL=true`; Neon �?`TOMORROWOS_STORE=postgres` + `DATABASE_SSL=true`; SQLite �?`TOMORROWOS_STORE=sqlite` (no `DATABASE_SSL` required).
 5. **Do not invent** Cloudinary credentials, database URLs, Vercel Blob tokens, brand colours, **or LLM API keys**.
 6. **Postgres env naming:** prefer **`SUPABASE_URL`** for Supabase; prefer **`DATABASE_URL`** for Neon.
 7. **Always prefer pooled connection strings** (Supabase Session pooler **6543**; Neon pooled host).
@@ -203,63 +203,63 @@ Then ask **Question 1**.
 12. **Enable Fluid compute** for Production WebSockets.
 13. **Production:** `api/index.ts` exports `http.Server` from `TomorrowOS.listen`. Not `next start`. No second TomorrowOS in `api/ws.ts`.
 14. **Preview:** Next reverse-proxy shell when v0 is Next-hardwired.
-15. After Q&A: **configure → install → deploy → minimal verify**.
+15. After Q&A: **configure �?install �?deploy �?minimal verify**.
 16. **No inventing CMS login** from a branding URL.
-17. **Skip ≠ invent.** Stay on Q1–Q3 only.
+17. **Skip �?invent.** Stay on Q1–Q3 only.
 18. **Publish gate:** `/status` JSON + WebSocket 101; no static `public/` trap.
 
-**Question order:** Q1 → (auto-set store env) → Q2 → Q3 → execution checklist.
+**Question order:** Q1 �?(auto-set store env) �?Q2 �?Q3 �?execution checklist.
 
 ---
 
-## Scheme A — Vercel Functions + WebSockets (mandatory for Production)
+## Scheme A �?Vercel Functions + WebSockets (mandatory for Production)
 
 > **Goal:** Preview may use Next + proxy; **Publish** runs TomorrowOS as a **Vercel Function** (`api/index.ts`) on **Fluid**, with WebSocket support per [Vercel WebSockets docs](https://vercel.com/docs/functions/websockets).  
 > **Scope:** Layout + `vercel.json` + dashboard. Prefer `npx @tomorrowos/sdk init --hosting v0` (`cms-starter-v0`).  
-> **Do not** break Replit/Railway: those keep using default `init` → `cms-starter` (root `server.ts` + `server.listen`, no `api/`).
+> **Do not** break Replit/Railway: those keep using default `init` �?`cms-starter` (root `server.ts` + `server.listen`, no `api/`).
 
 ### Why Scheme A exists
 
 | Layer | Preview (v0) | Publish (Production) |
 |-------|----------------|----------------------|
-| Host | Next.js shell + HTTP proxy | **Vercel Function** `api/index.ts` → `export default server` |
-| Static UI | Proxied from TomorrowOS | Served by **`staticRoot`** (`cms-panel/`) inside `listen()` — **not** Vercel Output Directory |
-| WebSocket | Optional / may fail in Preview | **Required** — Fluid Function upgrade (`wss://` → `/` rewritten to `/api`, or direct `/api`) |
+| Host | Next.js shell + HTTP proxy | **Vercel Function** `api/index.ts` �?`export default server` |
+| Static UI | Proxied from TomorrowOS | Served by **`staticRoot`** (`cms-panel/`) inside `listen()` �?**not** Vercel Output Directory |
+| WebSocket | Optional / may fail in Preview | **Required** �?Fluid Function upgrade (`wss://` �?`/` rewritten to `/api`, or direct `/api`) |
 | Next files | Allowed under `preview/` | **Must not** live at project root |
 
-**Root cause of “Control Panel works, TV cannot connect”:** HTTP can be served without WebSocket upgrades. Classic root-only `server.ts` / plain serverless handlers often return **200 HTML** on `Upgrade` instead of **101**. Official pattern is a Function that exports `http.Server` with `ws` attached ([docs](https://vercel.com/docs/functions/websockets)).
+**Root cause of “Control Panel works, TV cannot connect�?** HTTP can be served without WebSocket upgrades. Classic root-only `server.ts` / plain serverless handlers often return **200 HTML** on `Upgrade` instead of **101**. Official pattern is a Function that exports `http.Server` with `ws` attached ([docs](https://vercel.com/docs/functions/websockets)).
 
-### A1 — Project layout (Agent must enforce)
+### A1 �?Project layout (Agent must enforce)
 
 **Production (Vercel / v0 starter):**
 
 ```
-cms-app.ts         ← shared TomorrowOS.listen + export const server
-api/index.ts       ← export { server as default } from "../cms-app.js"
-server.ts          ← local/Preview: same default export (npm start / internal port)
-vercel.json        ← fluid + rewrites + functions.maxDuration
+cms-app.ts         �?shared TomorrowOS.listen + export const server
+api/index.ts       �?export { server as default } from "../cms-app.js"
+server.ts          �?local/Preview: same default export (npm start / internal port)
+vercel.json        �?fluid + rewrites + functions.maxDuration
 package.json
 brand.json
-cms-panel/         ← CMS static UI (NOT named public/ — avoids static-output trap)
-preview/           ← Next proxy for v0 Preview only
+cms-panel/         �?CMS static UI (NOT named public/ �?avoids static-output trap)
+preview/           �?Next proxy for v0 Preview only
 ```
 
-**Preview only — keep ALL Next under `preview/`:**
+**Preview only �?keep ALL Next under `preview/`:**
 
 ```
 preview/
   next.config.mjs
   app/
-  …
+  �?
 ```
 
 **Do NOT:**
 
-- ❌ Leave `next.config.mjs` + `app/` at project root
-- ❌ Set Output Directory to `public`, `cms-panel`, or `.`
-- ❌ Create a **second** TomorrowOS instance in `api/ws.ts` (separate isolate = broken pairing memory)
-- ❌ Use `(req, res) =>` serverless handlers that drop `upgrade`
-- ❌ Put `startCommand` / `processes` in `vercel.json` (v0 schema rejects them)
+- �?Leave `next.config.mjs` + `app/` at project root
+- �?Set Output Directory to `public`, `cms-panel`, or `.`
+- �?Create a **second** TomorrowOS instance in `api/ws.ts` (separate isolate = broken pairing memory)
+- �?Use `(req, res) =>` serverless handlers that drop `upgrade`
+- �?Put `startCommand` / `processes` in `vercel.json` (v0 schema rejects them)
 
 **`package.json` scripts:**
 
@@ -276,10 +276,10 @@ preview/
 }
 ```
 
-- **Local / Railway-style:** `npm start` → `tsx server.ts` → SDK calls `server.listen` (no `VERCEL` env).
+- **Local / Railway-style:** `npm start` �?`tsx server.ts` �?SDK calls `server.listen` (no `VERCEL` env).
 - **Vercel Production:** Function loads `api/index.ts`; SDK skips `listen` when `process.env.VERCEL` is set and Vercel owns the socket.
 
-### A2 — Function entry (matches Vercel WebSockets docs)
+### A2 �?Function entry (matches Vercel WebSockets docs)
 
 ```ts
 // api/index.ts
@@ -299,10 +299,10 @@ export { server, tomorrowos };
 SDK behaviour (0.9.32+):
 
 - Accepts WebSocket upgrades on `/`, `/api`, `/api/ws` (players may use either)
-- When `VERCEL` is set: **`autoListen` defaults to false** — do not bind a port yourself
+- When `VERCEL` is set: **`autoListen` defaults to false** �?do not bind a port yourself
 - Pattern aligns with docs: create `http.Server`, attach `ws`, **`export default server`**
 
-### A3 — `vercel.json` (Production)
+### A3 �?`vercel.json` (Production)
 
 ```json
 {
@@ -323,7 +323,7 @@ SDK behaviour (0.9.32+):
 }
 ```
 
-**`maxDuration` plan limits:** Hobby / many default plans allow **1–300** seconds. **800** requires a higher Vercel plan. Prefer **`300`** unless the account already allows more — otherwise Publish fails with *“maxDuration must be between 1 and 300… upgrade your plan”*.
+**`maxDuration` plan limits:** Hobby / many default plans allow **1�?00** seconds. **800** requires a higher Vercel plan. Prefer **`300`** unless the account already allows more �?otherwise Publish fails with *“maxDuration must be between 1 and 300�?upgrade your plan�?.
 
 **Why rewrites:** Public URLs stay `https://app.vercel.app/` and `/status` while the Function mount is `/api`. Device `wss://app.vercel.app/` is rewritten to the same Function so one isolate handles HTTP + WS.
 
@@ -333,24 +333,24 @@ SDK behaviour (0.9.32+):
 
 - `"fluid": true` is required for WebSockets
 - **Do not** set `outputDirectory` to `cms-panel` / `public`
-- `"buildCommand"` = no-op — **never** `next build` for Production
+- `"buildCommand"` = no-op �?**never** `next build` for Production
 - Dashboard Output Directory must stay **empty**
 
-### A4 — Vercel Project Settings (dashboard — mandatory)
+### A4 �?Vercel Project Settings (dashboard �?mandatory)
 
 | Setting | Required value |
 |---------|----------------|
-| Framework Preset | **Other** / null — **not Next.js** |
+| Framework Preset | **Other** / null �?**not Next.js** |
 | Install Command | `npm install` |
 | Build Command | `npm run build` (no-op) |
 | **Output Directory** | **empty** |
 | Fluid compute | **On** |
-| WebSockets | Account must allow Functions WebSockets (see docs “Permissions Required”) |
+| WebSockets | Account must allow Functions WebSockets (see docs “Permissions Required�? |
 
-### A5 — Publish acceptance (all must pass)
+### A5 �?Publish acceptance (all must pass)
 
-1. `curl -s https://PROD/status` → JSON (`{"status":...}`)
-2. `curl -s https://PROD/` → Control Panel HTML
+1. `curl -s https://PROD/status` �?JSON (`{"status":...}`)
+2. `curl -s https://PROD/` �?Control Panel HTML
 3. **WebSocket upgrade returns 101**, not 200 HTML:
 
 ```bash
@@ -365,28 +365,28 @@ curl.exe -i --http1.1 ^
 4. Control Panel does **not** show CMS unreachable / `Unexpected token 'T'`
 5. Fluid on; Framework = Other
 
-If (1)+(2) pass but (3) fails → Function is serving HTTP only. Re-check Fluid, `api/index.ts` default export, rewrites, and WebSockets permission. **Do not** invent a second `api/ws.ts` TomorrowOS instance.
+If (1)+(2) pass but (3) fails �?Function is serving HTTP only. Re-check Fluid, `api/index.ts` default export, rewrites, and WebSockets permission. **Do not** invent a second `api/ws.ts` TomorrowOS instance.
 
-### A6 — What Scheme A does **not** require
+### A6 �?What Scheme A does **not** require
 
-- ❌ No Next.js as Production CMS
-- ❌ No replacing SDK transport with hand-rolled pairing
-- ❌ No SQLite as production store on Vercel
-- ❌ No changes to Replit `cms-starter` layout for Vercel-only fixes
+- �?No Next.js as Production CMS
+- �?No replacing SDK transport with hand-rolled pairing
+- �?No SQLite as production store on Vercel
+- �?No changes to Replit `cms-starter` layout for Vercel-only fixes
 
-### A7 — If v0 Publish still fails (Path B / C)
+### A7 �?If v0 Publish still fails (Path B / C)
 
 **Path B:** Deploy with `vercel --prod` or Git integration (full Vercel), same Scheme A layout.
 
 **Path C:** Host CMS on **Railway / Fly.io / Replit** (long-lived Node). Use Vercel only for Preview if needed.
 
-### A8 — Migrate an existing broken Vercel project
+### A8 �?Migrate an existing broken Vercel project
 
 1. Scaffold/compare with `cms-starter-v0` (`init --hosting v0`) or copy:
    - `cms-app.ts`, `api/index.ts`, `server.ts`, `vercel.json`
-   - rename `public/` → `cms-panel/` if still present
+   - rename `public/` �?`cms-panel/` if still present
 2. Ensure **one** Function exports the **same** `server` from `cms-app.ts`
-3. Fluid on → Redeploy
+3. Fluid on �?Redeploy
 4. Verify A5 (especially WebSocket 101)
 5. On TVs: enter `https://YOUR.vercel.app/` (players also try `/api` automatically on vercel.app hosts)
 
@@ -396,7 +396,7 @@ If (1)+(2) pass but (3) fails → Function is serving HTTP only. Re-check Fluid,
 
 ### Production runtime (Publish)
 
-- Serve TomorrowOS via **Vercel Function** `api/index.ts` → `export default server` (Fluid + WebSockets).
+- Serve TomorrowOS via **Vercel Function** `api/index.ts` �?`export default server` (Fluid + WebSockets).
 - Keep root **`server.ts`** for **local** `npm start` / Preview internal port only (same `cms-app.ts`).
 - Keep **`@tomorrowos/sdk`** (0.9.32+) and put **`tsx` in `dependencies`** for local start.
 - Node **20+**.
@@ -456,7 +456,7 @@ Add `@vercel/blob` only when the user chooses **Vercel Blob** in Question 2.
 
 For Preview shell only, add as needed: `next`, `react`, `react-dom`, and a process runner (`concurrently` or equivalent). These must **not** become the Production CMS.
 
-### `server.ts` pattern (Vercel-adapted — Production)
+### `server.ts` pattern (Vercel-adapted �?Production)
 
 Keep the server at **project root** (e.g. `server.ts` / `server.mts`). Do **not** move Production into `api/` solely to satisfy Vercel routing myths.
 
@@ -496,14 +496,14 @@ const server = tomorrowos.listen({
 export default server;
 ```
 
-- **Production:** `PORT` from Vercel → TomorrowOS listens on that port (no Next).
+- **Production:** `PORT` from Vercel �?TomorrowOS listens on that port (no Next).
 - **Preview:** set `TOMORROWOS_INTERNAL_PORT=3001` (or similar) so Next can own `:3000` and proxy inward.
 
 Load env with `dotenv` for local/`vercel dev`. On production Deploy, Vercel injects Environment Variables natively.
 
-### Preview adapter (v0 / Next reverse proxy) — required when Preview is Next-hardwired
+### Preview adapter (v0 / Next reverse proxy) �?required when Preview is Next-hardwired
 
-Detect Preview / v0 (Next already present, or Preview blank while TomorrowOS logs “listening”). Then:
+Detect Preview / v0 (Next already present, or Preview blank while TomorrowOS logs “listening�?. Then:
 
 1. Keep a **minimal** Next app **isolated when possible** (e.g. under `preview/`) so Production Framework detection does not latch onto root `next.config.*`.
 2. TomorrowOS listens on **`127.0.0.1:TOMORROWOS_INTERNAL_PORT`** (default **3001**).
@@ -526,9 +526,9 @@ Preferred UX: proxy **`/`** itself (rewrites) so the Preview URL shows the Contr
 - Deleting TomorrowOS `server.ts` because Preview needed Next.
 - Claiming setup complete if Production entrypoint is still `next start`.
 - Claiming setup complete if Production `GET /` is `404: NOT_FOUND`.
-- Creating root `api/index.*` + `routes` catch-all that exports a raw `http.Server` “to fix 404”.
+- Creating root `api/index.*` + `routes` catch-all that exports a raw `http.Server` “to fix 404�?
 
-### `vercel.json` (Production — explicit Node, not Next)
+### `vercel.json` (Production �?explicit Node, not Next)
 
 Write `vercel.json` so Production cannot be mistaken for Next. Minimum:
 
@@ -545,23 +545,23 @@ Use `pnpm` / `yarn` variants of install/build if that is the project’s package
 
 **Do not** add `startCommand`, `processes`, or `outputDirectory` to `vercel.json` when v0 schema rejects them. Start = `package.json` `"start": "tsx server.ts"`. Output Directory = **empty in dashboard**.
 
-**Also force Project Settings (dashboard or Vercel API) — this is mandatory (see Scheme A4):**
+**Also force Project Settings (dashboard or Vercel API) �?this is mandatory (see Scheme A4):**
 
 | Setting | Required value |
 |---------|----------------|
-| Framework Preset | **Other** / null — **not Next.js** |
+| Framework Preset | **Other** / null �?**not Next.js** |
 | Install Command | `npm install` (or pnpm/yarn) |
 | Build Command | `npm run build` (no-op exit 0) |
-| Output Directory | **empty / null** — **NOT `public`** |
-| Start Command | `npm run start` → `tsx server.ts` (or `.mts`) — set in **dashboard**, not `vercel.json` |
+| Output Directory | **empty / null** �?**NOT `public`** |
+| Start Command | `npm run start` �?`tsx server.ts` (or `.mts`) �?set in **dashboard**, not `vercel.json` |
 | Fluid compute | **On** |
 
 If `next` / `next.config.*` exist for Preview and the dashboard still auto-selects Next.js:
 
 1. Patch Framework Preset to **Other** via API/CLI/dashboard.
 2. Redeploy.
-3. Hit Production `GET /status` — must be **JSON**, not HTML.
-4. Hit Production `GET /` — must be Control Panel HTML, not `404: NOT_FOUND`.
+3. Hit Production `GET /status` �?must be **JSON**, not HTML.
+4. Hit Production `GET /` �?must be Control Panel HTML, not `404: NOT_FOUND`.
 
 If Vercel’s UI and this file disagree on bundling, **prefer whatever keeps a single long-lived Node HTTP server with WebSocket upgrade on `/` for Production**. Document the adaptation in the final summary.
 
@@ -574,15 +574,15 @@ If Vercel’s UI and this file disagree on bundling, **prefer whatever keeps a s
 
 ### What not to create
 
-- ❌ `.replit`, `.replit-artifact`
-- ❌ Next.js as the **Production** CMS (App Router replacing TomorrowOS)
-- ❌ Root `api/` catch-all exporting raw `http.Server` to “fix” Publish 404
-- ❌ Separate “API project” without the Control Panel
-- ❌ Committing database passwords, Cloudinary secrets, or Blob tokens
+- �?`.replit`, `.replit-artifact`
+- �?Next.js as the **Production** CMS (App Router replacing TomorrowOS)
+- �?Root `api/` catch-all exporting raw `http.Server` to “fix�?Publish 404
+- �?Separate “API project�?without the Control Panel
+- �?Committing database passwords, Cloudinary secrets, or Blob tokens
 
 ---
 
-## Question 1 — Database (always)
+## Question 1 �?Database (always)
 
 > **Do not** ask screen counts. Present all three options; recommend **Supabase** for Vercel fleets.  
 > **After the user picks a database:** collect the URL if needed, then **you** set `TOMORROWOS_STORE` + `DATABASE_SSL` (see mapping below). The customer must **never** be asked to type those two names or values.
@@ -595,71 +595,71 @@ If Vercel’s UI and this file disagree on bundling, **prefer whatever keeps a s
 | 2 Neon | `TOMORROWOS_STORE=postgres`, `DATABASE_SSL=true` | `DATABASE_URL` (pooled string) |
 | 3 SQLite | `TOMORROWOS_STORE=sqlite` | Confirmation only |
 
-If you open an Env configuration UI for Q1, fields visible to the user may include **only** `SUPABASE_URL` or `DATABASE_URL`. **Do not** show blank `TOMORROWOS_STORE` / `DATABASE_SSL` inputs — write those yourself in the same step.
+If you open an Env configuration UI for Q1, fields visible to the user may include **only** `SUPABASE_URL` or `DATABASE_URL`. **Do not** show blank `TOMORROWOS_STORE` / `DATABASE_SSL` inputs �?write those yourself in the same step.
 
-### Step A — Ask storage choice
+### Step A �?Ask storage choice
 
 **Ask exactly:**
 
 > Which database should TomorrowOS use on Vercel?
 >
-> **1. Supabase Postgres (recommended)** — durable pairing/playlists; use the **Session pooler** URL (`*.pooler.supabase.com:6543`).
+> **1. Supabase Postgres (recommended)** �?durable pairing/playlists; use the **Session pooler** URL (`*.pooler.supabase.com:6543`).
 >
-> **2. Neon Postgres** — serverless Postgres native to Vercel; use Neon’s **pooled** connection string from the Neon dashboard (not the direct un-pooled host for serverless).
+> **2. Neon Postgres** �?serverless Postgres native to Vercel; use Neon’s **pooled** connection string from the Neon dashboard (not the direct un-pooled host for serverless).
 >
-> **3. SQLite (`data/tomorrowos.db`)** — **demo / local only on Vercel.** The filesystem is ephemeral; pairings and playlists will not survive redeploys. Only choose this if you understand the limitation.
+> **3. SQLite (`data/tomorrowos.db`)** �?**demo / local only on Vercel.** The filesystem is ephemeral; pairings and playlists will not survive redeploys. Only choose this if you understand the limitation.
 >
-> Reply with **1**, **2**, or **3** (or “Supabase” / “Neon” / “SQLite”).
+> Reply with **1**, **2**, or **3** (or “Supabase�?/ “Neon�?/ “SQLite�?.
 
-### Step B — If **1 / Supabase**
+### Step B �?If **1 / Supabase**
 
-**Ask exactly (connection string only — not TOMORROWOS_STORE / DATABASE_SSL):**
+**Ask exactly (connection string only �?not TOMORROWOS_STORE / DATABASE_SSL):**
 
 > Paste your Supabase Postgres connection string. I will store it as **`SUPABASE_URL`**. I will set **`TOMORROWOS_STORE`** and **`DATABASE_SSL`** for you automatically.
 >
-> In Supabase: **Project Settings → Database → Connection string → Connection pooling** (Session mode).  
+> In Supabase: **Project Settings �?Database �?Connection string �?Connection pooling** (Session mode).  
 > Preferred shape:  
 > `postgresql://postgres.[PROJECT]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:6543/postgres`
 >
 > **Do not** use the direct host `db.*.supabase.co:5432` for Vercel.
 
-**You must then (automatic — do NOT ask the user to type store/ssl vars):**
+**You must then (automatic �?do NOT ask the user to type store/ssl vars):**
 
 1. Set Vercel Env Vars in one step:
-   - `SUPABASE_URL=<user pooler string>` ← from user
-   - `TOMORROWOS_STORE=supabase` ← **you set; never ask**
-   - `DATABASE_SSL=true` ← **you set; never ask**
+   - `SUPABASE_URL=<user pooler string>` �?from user
+   - `TOMORROWOS_STORE=supabase` �?**you set; never ask**
+   - `DATABASE_SSL=true` �?**you set; never ask**
 2. Wire `cms-app.ts` / `server.ts` store as in **Runtime & Vercel deploy rules**.
 3. Optional committed `.env.example` with **placeholders only**.
 4. **Do not** commit the real connection string.
 5. **Do not** open a form whose blank fields include `TOMORROWOS_STORE` or `DATABASE_SSL`.
 
-### Step C — If **2 / Neon**
+### Step C �?If **2 / Neon**
 
 **Ask exactly (connection string only):**
 
 > Paste your **Neon pooled** Postgres connection string. I will store it as **`DATABASE_URL`**. I will set **`TOMORROWOS_STORE`** and **`DATABASE_SSL`** for you automatically.
 >
-> In Neon: **Dashboard → Connection details → Pooled connection**.  
+> In Neon: **Dashboard �?Connection details �?Pooled connection**.  
 > Typical shape:  
 > `postgresql://[user]:[password]@[endpoint]-pooler.[region].aws.neon.tech/[dbname]?sslmode=require`
 
 **You must then (automatic):**
 
 1. Set Vercel Env Vars:
-   - `DATABASE_URL=<user pooled string>` ← from user
-   - `TOMORROWOS_STORE=postgres` ← **you set; never ask**
-   - `DATABASE_SSL=true` ← **you set; never ask**
+   - `DATABASE_URL=<user pooled string>` �?from user
+   - `TOMORROWOS_STORE=postgres` �?**you set; never ask**
+   - `DATABASE_SSL=true` �?**you set; never ask**
 2. Wire `createTomorrowOSStore` for Postgres.
 3. **Do not** commit the real connection string.
 4. **Do not** ask the user to fill `TOMORROWOS_STORE` or `DATABASE_SSL` in chat or Env UI.
 5. If you see `ENETUNREACH` on `:5432`, switch to Neon’s **pooled** URL.
 
-### Step D — If **3 / SQLite**
+### Step D �?If **3 / SQLite**
 
 **Warn exactly before continuing:**
 
-> SQLite on Vercel is **not** suitable for production fleets — data in `data/tomorrowos.db` is lost when the instance is recycled or redeployed. Continue only for a quick demo.
+> SQLite on Vercel is **not** suitable for production fleets �?data in `data/tomorrowos.db` is lost when the instance is recycled or redeployed. Continue only for a quick demo.
 
 Only proceed after the user explicitly confirms.
 
@@ -673,29 +673,29 @@ Only proceed after the user explicitly confirms.
 
 ---
 
-## Question 2 — Media storage
+## Question 2 �?Media storage
 
 > **This question is only about media files (images/videos).**  
-> It is **not** about OpenAI, AI pairing, or LLM keys. If you are about to ask for an `sk-` key, **stop** — you are off-protocol.  
-> **Copy the three options below verbatim.** Wrong examples that must **never** appear: “Vercel Blob (recommended)”, “Supabase Storage”, “No media storage / disable uploads”.
+> It is **not** about OpenAI, AI pairing, or LLM keys. If you are about to ask for an `sk-` key, **stop** �?you are off-protocol.  
+> **Copy the three options below verbatim.** Wrong examples that must **never** appear: “Vercel Blob (recommended)�? “Supabase Storage�? “No media storage / disable uploads�?
 
-### Step A — Ask storage choice
+### Step A �?Ask storage choice
 
-**Ask exactly (wording must match — Cloudinary is recommended):**
+**Ask exactly (wording must match �?Cloudinary is recommended):**
 
 > How should playlist media (images/videos) be stored?
 >
-> **1. Cloudinary (recommended)** — durable public HTTPS URLs (`https://res.cloudinary.com/...`). Works out of the box with `@tomorrowos/sdk` auto-detection. **Prefer this on Vercel.**
+> **1. Cloudinary (recommended)** �?durable public HTTPS URLs (`https://res.cloudinary.com/...`). Works out of the box with `@tomorrowos/sdk` auto-detection. **Prefer this on Vercel.**
 >
-> **2. Vercel Blob** — Vercel-native object storage; durable `https://*.public.blob.vercel-storage.com/...` URLs. Use when you want media on the same Vercel project without a Cloudinary account.
+> **2. Vercel Blob** �?Vercel-native object storage; durable `https://*.public.blob.vercel-storage.com/...` URLs. Use when you want media on the same Vercel project without a Cloudinary account.
 >
-> **3. Local disk only** — `cms-panel/uploads` or `public/uploads` (OK for quick local tests; **not** for production Vercel fleets — files are ephemeral).
+> **3. Local disk only** �?`cms-panel/uploads` or `public/uploads` (OK for quick local tests; **not** for production Vercel fleets �?files are ephemeral).
 >
-> Reply with **1**, **2**, or **3** (or “Cloudinary” / “Vercel Blob” / “local”).
+> Reply with **1**, **2**, or **3** (or “Cloudinary�?/ “Vercel Blob�?/ “local�?.
 
-If you catch yourself about to offer Blob-as-recommended, Supabase Storage, or “no media”, **stop and paste the block above instead**.
+If you catch yourself about to offer Blob-as-recommended, Supabase Storage, or “no media�? **stop and paste the block above instead**.
 
-### Step B — If **1 / Cloudinary** (same Question 2 — **one Env popup**)
+### Step B �?If **1 / Cloudinary** (same Question 2 �?**one Env popup**)
 
 > **Critical UX rule:** Immediately open the **Vercel Environment Variables configuration popup / form** with **all Cloudinary fields in one UI**. Do **not** ask for cloud name, then key, then secret in separate chat messages.
 
@@ -726,13 +726,13 @@ If you catch yourself about to offer Blob-as-recommended, Supabase Storage, or
 
 The SDK auto-detects these env vars.
 
-### Step C — If **2 / Vercel Blob** (same Question 2)
+### Step C �?If **2 / Vercel Blob** (same Question 2)
 
 **Ask exactly:**
 
 > I will enable **Vercel Blob** for media uploads.
 >
-> 1. In the Vercel project: **Storage → Create → Blob** (or link an existing Blob store to this project).
+> 1. In the Vercel project: **Storage �?Create �?Blob** (or link an existing Blob store to this project).
 > 2. Confirm **`BLOB_READ_WRITE_TOKEN`** is available (Vercel usually injects it when Blob is linked).
 >
 > Paste the token only if it is not already set in your project Env Vars. Do you already have Blob linked on this Vercel project? (yes / no)
@@ -749,57 +749,57 @@ The SDK auto-detects these env vars.
 import { put } from "@vercel/blob";
 
 // On upload: const blob = await put(filename, body, { access: "public", token: process.env.BLOB_READ_WRITE_TOKEN });
-// Store blob.url in uploaded_assets — same shape as Cloudinary secure URLs.
+// Store blob.url in uploaded_assets �?same shape as Cloudinary secure URLs.
 ```
 
-4. Warn: until the project’s Blob bridge is wired, Control Panel **Media** status may show local/ephemeral — verify uploads return `https://*.blob.vercel-storage.com/...` before calling setup complete.
+4. Warn: until the project’s Blob bridge is wired, Control Panel **Media** status may show local/ephemeral �?verify uploads return `https://*.blob.vercel-storage.com/...` before calling setup complete.
 5. Do **not** proceed to Question 3 until `BLOB_READ_WRITE_TOKEN` exists (or Blob is linked and token is confirmed in the Vercel dashboard).
 
-### Step D — If **3 / local uploads**
+### Step D �?If **3 / local uploads**
 
 1. `mkdir -p public/uploads`
-2. Warn clearly: files may vanish on redeploy; players need stable HTTPS URLs — Cloudinary or Vercel Blob is strongly preferred for Vercel.
+2. Warn clearly: files may vanish on redeploy; players need stable HTTPS URLs �?Cloudinary or Vercel Blob is strongly preferred for Vercel.
 
 ---
 
-## Question 3 — Brand (`brand.json` only)
+## Question 3 �?Brand (`brand.json` only)
 
 > Updates **only** `brand.json`. Does **not** change Vercel project settings, Env Vars, or `server.ts` store wiring beyond what Q1–Q2 already required.
 >
-> **IRON RULE — website URL ≠ build a website / login / auth CMS.**  
-> If the user pastes a URL (or says “make it look like this site”), that input is **reference material for `brand.json` only** (name, colours, fonts, logo, tagline).  
-> **Do not** scaffold a login page, signup, OAuth, gated dashboard, or copy the reference site’s IA/pages — **unless the user explicitly asks for CMS login / auth**.  
+> **IRON RULE �?website URL �?build a website / login / auth CMS.**  
+> If the user pastes a URL (or says “make it look like this site�?, that input is **reference material for `brand.json` only** (name, colours, fonts, logo, tagline).  
+> **Do not** scaffold a login page, signup, OAuth, gated dashboard, or copy the reference site’s IA/pages �?**unless the user explicitly asks for CMS login / auth**.  
 > Default TomorrowOS Control Panel has **no login**. Keep it that way.
 
-### Step A — Ask branding input
+### Step A �?Ask branding input
 
 **Ask exactly:**
 
 > Let’s brand your TomorrowOS experience. You can answer in either way:
 >
-> **Option A — Website URL only (brand reference)**  
+> **Option A �?Website URL only (brand reference)**  
 > Paste **one public website URL**. I will use it **only** to infer colours, fonts, name, tagline, and logo for **`brand.json`**.  
-> I will **not** rebuild that website, add a login page, or change Control Panel features — unless you explicitly ask for login/auth later.
+> I will **not** rebuild that website, add a login page, or change Control Panel features �?unless you explicitly ask for login/auth later.
 >
-> **Option B — Manual fields**  
+> **Option B �?Manual fields**  
 > Provide:
 > 1. **Product / venue name**
 > 2. **Tagline** (optional)
 > 3. **Primary colour** (hex, e.g. `#FF8A3D`)
-> 4. **Background colour** (hex, optional — default `#FAFAF9`)
-> 5. **Text colour** (hex, optional — default `#0A0908`)
+> 4. **Background colour** (hex, optional �?default `#FAFAF9`)
+> 5. **Text colour** (hex, optional �?default `#0A0908`)
 > 6. **Secondary / accent colour** (hex, optional)
-> 7. **Logo** — upload SVG/PNG into the project, or a URL I can fetch into `./assets/`
+> 7. **Logo** �?upload SVG/PNG into the project, or a URL I can fetch into `./assets/`
 
-### Step B — If the user gives **only a website URL** (Option A)
+### Step B �?If the user gives **only a website URL** (Option A)
 
 **You must:**
 
 1. **Fetch and inspect** the page (HTTP GET the URL; follow one redirect if needed). Do not invent colours.
 2. **Write / update `brand.json` only** from what you infer. Touch nothing else for this step (no new pages, no auth, no Next marketing site, no login UI).
 3. **Derive branding** using this priority order:
-   - **Name:** `<title>`, `og:site_name`, or prominent header / logo `alt` text (trim to ≤ 60 chars).
-   - **Tagline:** `meta[name="description"]`, `og:description`, or first hero subtitle (≤ 120 chars).
+   - **Name:** `<title>`, `og:site_name`, or prominent header / logo `alt` text (trim to �?60 chars).
+   - **Tagline:** `meta[name="description"]`, `og:description`, or first hero subtitle (�?120 chars).
    - **Primary colour:** `meta[name="theme-color"]`, CSS `--primary` / `--brand` variables, or dominant accent from linked stylesheets / inline styles (convert to `#RRGGBB`).
    - **Background colour:** `body` / `:root` background (default `#FAFAF9` if light site).
    - **Text colour:** main body text colour (default `#0A0908` if light site).
@@ -808,20 +808,20 @@ import { put } from "@vercel/blob";
    - **Logo:** prefer `og:image`, then `link[rel="icon"]` / apple-touch-icon, then header `<img>` logo. Download into `./assets/logo.png` or `./assets/logo.svg` and set `logoPath` accordingly. If only favicon exists, use it and note size in the summary.
 4. **Contrast check:** if background is dark, set `activationScreen.theme` to `"dark"` and add `logoPathOnDark` when a light logo variant exists.
 5. **Infer `cms.useCase`** from page content when obvious (restaurant / retail / corporate / etc.); otherwise `"other"`.
-6. **Show a one-line summary** to the user (name + primary hex + logo path) before or while writing the file — do not ask a second branding question unless fetch failed.
+6. **Show a one-line summary** to the user (name + primary hex + logo path) before or while writing the file �?do not ask a second branding question unless fetch failed.
 7. If the URL is unreachable, blocked, or has no usable styles, say so and fall back to **Option B** manual questions for missing fields only.
 
 **Explicitly forbidden when the user only gave a URL (no login request):**
 
-- ❌ Login / signup / “Sign in to continue” screens
-- ❌ Auth middleware, sessions, cookies, OAuth, password forms
-- ❌ Cloning the reference site as a marketing landing or multi-page CMS
-- ❌ Gating the Control Panel behind authentication
-- ❌ Treating “make it like this site” as “rebuild this site”
+- �?Login / signup / “Sign in to continue�?screens
+- �?Auth middleware, sessions, cookies, OAuth, password forms
+- �?Cloning the reference site as a marketing landing or multi-page CMS
+- �?Gating the Control Panel behind authentication
+- �?Treating “make it like this site�?as “rebuild this site�?
 
-If the reference site itself is a login page, **still only extract visual brand tokens** (colours/logo/name) into `brand.json` — do **not** recreate that login flow.
+If the reference site itself is a login page, **still only extract visual brand tokens** (colours/logo/name) into `brand.json` �?do **not** recreate that login flow.
 
-### Step C — Write `brand.json`
+### Step C �?Write `brand.json`
 
 Validate mentally against `brand.schema.json`. Minimum:
 
@@ -851,11 +851,11 @@ Validate mentally against `brand.schema.json`. Minimum:
 }
 ```
 
-Always set **`cms.hostingTarget`: `"vercel"`** without asking. Default `expectedScreens` to `5` unless the user already volunteered a number. Set `cmsEndpoint` only if they already know the public `https://…vercel.app` URL; otherwise tell them to pair TVs with the **Published** HTTPS origin (player maps `https://` → `wss://`).
+Always set **`cms.hostingTarget`: `"vercel"`** without asking. Default `expectedScreens` to `5` unless the user already volunteered a number. Set `cmsEndpoint` only if they already know the public `https://…vercel.app` URL; otherwise tell them to pair TVs with the **Published** HTTPS origin (player maps `https://` �?`wss://`).
 
 ---
 
-## After all answers — execution checklist
+## After all answers �?execution checklist
 
 ### A. Seed the project
 
@@ -865,11 +865,11 @@ npx @tomorrowos/sdk@latest init .
 # npx @tomorrowos/sdk@latest init . --force
 ```
 
-Then (**Scheme A — mandatory for Publish**):
+Then (**Scheme A �?mandatory for Publish**):
 
 1. Keep **`server.ts`** at **project root** with top-level `listen()` + `export default server`.
-2. If Preview needs Next: **move** `next.config.*`, `app/`, Next `tsconfig` / `postcss` / `next-env.d.ts` into **`preview/`** — remove them from root so Production is not mistaken for Next/static.
-3. Write `vercel.json` per **Scheme A3** (`fluid`, `framework: null`, no-op `buildCommand` — **no** `startCommand`).
+2. If Preview needs Next: **move** `next.config.*`, `app/`, Next `tsconfig` / `postcss` / `next-env.d.ts` into **`preview/`** �?remove them from root so Production is not mistaken for Next/static.
+3. Write `vercel.json` per **Scheme A3** (`fluid`, `framework: null`, no-op `buildCommand` �?**no** `startCommand`).
 4. **Force Project Settings** per **Scheme A4** (Framework = Other, Output Directory empty, Start = `npm run start`, Fluid on). Patch dashboard via API if it still says Next.js.
 5. Do **not** add root `api/` catch-all for raw `http.Server`.
 6. Do **not** add `.replit*`.
@@ -881,8 +881,8 @@ Then (**Scheme A — mandatory for Publish**):
 |------|----------|--------------|
 | `SUPABASE_URL` | If Q1 = Supabase | User pastes URL |
 | `DATABASE_URL` | If Q1 = Neon | User pastes URL |
-| `TOMORROWOS_STORE` | Yes | **Agent auto-sets only** — never a blank field for the user (`supabase` / `postgres` / `sqlite`) |
-| `DATABASE_SSL` | Yes for Postgres | **Agent auto-sets only** — never a blank field for the user (`true`) |
+| `TOMORROWOS_STORE` | Yes | **Agent auto-sets only** �?never a blank field for the user (`supabase` / `postgres` / `sqlite`) |
+| `DATABASE_SSL` | Yes for Postgres | **Agent auto-sets only** �?never a blank field for the user (`true`) |
 | `CLOUDINARY_*` | If Q2 = Cloudinary | User via **one Env popup** (all fields) |
 | `BLOB_READ_WRITE_TOKEN` | If Q2 = Vercel Blob | User / Blob link |
 | `TOMORROWOS_INTERNAL_PORT` | Preview only | Agent (e.g. `3001`) |
@@ -904,40 +904,40 @@ Confirm browser:
 - **Preview:** Control Panel visible through the Next proxy at `/`
 - **Production start:** Control Panel served directly by TomorrowOS at `/`
 
-### D. Deploy (Publish — Node only)
+### D. Deploy (Publish �?Node only)
 
 ```bash
 vercel --prod
-# or git push → Vercel Git integration
+# or git push �?Vercel Git integration
 ```
 
-**Publish acceptance checklist (all must pass — Scheme A5):**
+**Publish acceptance checklist (all must pass �?Scheme A5):**
 
-1. Framework Preset = **Other** / null (dashboard confirms — not Next.js)
+1. Framework Preset = **Other** / null (dashboard confirms �?not Next.js)
 2. Output Directory = **empty** (not `public`)
 3. Start Command = Node `TomorrowOS.listen` (`npm run start` / `tsx server.ts`)
 4. Fluid compute on
 5. Env Vars present for Production
-6. Production `GET /status` returns **JSON** — **not** HTML (`Unexpected token 'T'` means this failed)
-7. Production `GET /` returns Control Panel HTML — **not** `404: NOT_FOUND`
+6. Production `GET /status` returns **JSON** �?**not** HTML (`Unexpected token 'T'` means this failed)
+7. Production `GET /` returns Control Panel HTML �?**not** `404: NOT_FOUND`
 
-If step 6 fails but step 7 passes: **static `public/` trap** — Vercel is not running Node. Re-apply Scheme A3–A4; try **Path B** (Git / `vercel --prod`); do **not** invent `api/` + `rewrites`.
+If step 6 fails but step 7 passes: **static `public/` trap** �?Vercel is not running Node. Re-apply Scheme A3–A4; try **Path B** (Git / `vercel --prod`); do **not** invent `api/` + `rewrites`.
 
 Tell the user:
 
 - **Control Panel (Publish):** `https://YOUR-PROJECT.vercel.app`
 - **TV CMS endpoint:** same HTTPS origin (players use `wss://`)
-- **Preview:** Next shell is for v0 only — do not pair devices to Preview
+- **Preview:** Next shell is for v0 only �?do not pair devices to Preview
 
 ### E. Minimal verification only
 
 **Do:**
 
 1. Preview: Control Panel HTML at `/` (via Next proxy in `preview/` if applicable)
-2. Publish: `GET /status` → JSON; `GET /` → Control Panel from **Node** TomorrowOS
+2. Publish: `GET /status` �?JSON; `GET /` �?Control Panel from **Node** TomorrowOS
 3. Publish: panel does **not** show `Unexpected token 'T'` / CMS unreachable
 4. Server status: Media OK when Cloudinary or Blob configured
-5. Database: if ERROR shows **`ENETUNREACH` … IPv6 … `:5432`**, switch to **pooled** URL (Supabase `:6543` or Neon pooler) and redeploy — call this out explicitly to the user
+5. Database: if ERROR shows **`ENETUNREACH` �?IPv6 �?`:5432`**, switch to **pooled** URL (Supabase `:6543` or Neon pooler) and redeploy �?call this out explicitly to the user
 6. Fluid compute on for Production
 
 **Do not block** on long WebSocket/device pairing tests unless the user asks. Prefer pairing against **Publish**, not Preview.
@@ -949,25 +949,25 @@ Tell the user:
 | Symptom | Likely cause | Fix |
 |---------|--------------|-----|
 | Publish `404: NOT_FOUND` | Framework Preset still **Next.js** / no Function | Scheme A: Framework = **Other**, Fluid on, `api/index.ts` + rewrites; redeploy |
-| Panel loads but **CMS unreachable** / `Unexpected token 'T', "The page c"...` | **`public/` deployed as static site** — no Function | Rename to `cms-panel/`; Output empty; Scheme A Function entry; **Path B** if needed |
-| Only `/api/status` returns JSON, `/status` is 404 | Missing **rewrites** to `/api` | Add Scheme A3 rewrite `/(.*) → /api` (exclude existing `/api/`); redeploy |
+| Panel loads but **CMS unreachable** / `Unexpected token 'T', "The page c"...` | **`public/` deployed as static site** �?no Function | Rename to `cms-panel/`; Output empty; Scheme A Function entry; **Path B** if needed |
+| Only `/api/status` returns JSON, `/status` is 404 | Missing **rewrites** to `/api` | Add Scheme A3 rewrite `/(.*) �?/api` (exclude existing `/api/`); redeploy |
 | Control Panel OK, TV **could not connect** | WebSocket upgrade not reaching Function (200 HTML) | Fluid on; `export default server`; verify 101 on `/` and `/api`; check WebSockets permission |
 | `vercel.json` error: invalid `startCommand` | v0 schema rejects it | Remove from `vercel.json`; Function entry does not need startCommand |
-| Separate `api/ws.ts` with a second `new TomorrowOS` | Two isolates — pairing memory split | **One** Function only (`api/index.ts` → shared `cms-app.ts`) |
+| Separate `api/ws.ts` with a second `new TomorrowOS` | Two isolates �?pairing memory split | **One** Function only (`api/index.ts` �?shared `cms-app.ts`) |
 | `vercel inspect` shows Output = `public if it exists` | Framework=Other static default | Force Output Directory **empty**; use `cms-panel/`; Path B redeploy |
 | Build runs `next build` / missing routes-manifest | Next auto-detected from root `next.config` / `app/` | Move Next to `preview/`; Framework null/Other; `build` = no-op |
-| Preview blank but logs show TomorrowOS listening | v0 Next intercepts public port | Add Next reverse proxy → internal TomorrowOS port |
+| Preview blank but logs show TomorrowOS listening | v0 Next intercepts public port | Add Next reverse proxy �?internal TomorrowOS port |
 | Preview works, Publish broken / Next-only | Production still on Next | Switch Production to Fluid Function `api/index.ts` |
 | `ENETUNREACH` / IPv6 / `:5432` | Direct Postgres URL | Use **pooled** URL (Supabase `:6543` or Neon pooler) |
 | Control Panel OK, devices never stay paired after restart | SQLite / ephemeral disk | Use Supabase or Neon |
 | Uploads break / broken thumbs in prod | Local uploads only | Cloudinary or Vercel Blob |
-| Blob uploads 401 / missing token | Blob not linked | Vercel Storage → Blob + `BLOB_READ_WRITE_TOKEN` |
+| Blob uploads 401 / missing token | Blob not linked | Vercel Storage �?Blob + `BLOB_READ_WRITE_TOKEN` |
 | WebSocket fails on Publish | Fluid off / static-only / Next as Production / no Function WS | Enable Fluid; Scheme A; test 101 upgrade |
-| Devices fail only on Preview | Next proxy cannot upgrade `wss` | Expected — pair on Publish URL |
+| Devices fail only on Preview | Next proxy cannot upgrade `wss` | Expected �?pair on Publish URL |
 | Agent asked user to fill `TOMORROWOS_STORE` / `DATABASE_SSL` | Off-protocol | Agent must auto-set after DB choice; remove those fields from user Env forms |
-| Agent offered Blob-as-recommended / Supabase Storage / “no media” for Q2 | Invented options | Re-ask Q2 verbatim: **1 Cloudinary (recommended)**, 2 Blob, 3 local |
+| Agent offered Blob-as-recommended / Supabase Storage / “no media�?for Q2 | Invented options | Re-ask Q2 verbatim: **1 Cloudinary (recommended)**, 2 Blob, 3 local |
 | Agent asked Cloudinary key/secret in three chat turns | Off-protocol | Use **one Env popup** with all Cloudinary fields |
-| Agent asked for OpenAI / `sk-` key during setup | Hallucinated “AI pairing” requirement | **Refuse.** TomorrowOS does not need LLM keys. Return to Q2 media choices only |
+| Agent asked for OpenAI / `sk-` key during setup | Hallucinated “AI pairing�?requirement | **Refuse.** TomorrowOS does not need LLM keys. Return to Q2 media choices only |
 | Agent built a login page after user pasted a URL | Misread brand reference as product scope | Remove login; keep starter Control Panel; apply URL only to `brand.json` |
 | Secrets in git | Mistake | Rotate keys; move to Vercel Env Vars |
 | Replit files present | Copied wrong protocol | Delete `.replit*`; use this file |
@@ -985,22 +985,22 @@ Tell the user:
 | Media | Cloudinary or Replit Object Storage | Cloudinary **or Vercel Blob** |
 | Preview | Replit Preview / Autoscale Node | **Next shell + proxy** when v0 hardwires Next |
 | Publish | Long-lived Node | **Node `TomorrowOS.listen` only** (not Next); gate on no `404 NOT_FOUND` |
-| Brand from URL | Not in Replit protocol | **Option A** — infer **`brand.json` only**; never invent login |
+| Brand from URL | Not in Replit protocol | **Option A** �?infer **`brand.json` only**; never invent login |
 
 ---
 
-## Final summary template (Agent → human)
+## Final summary template (Agent �?human)
 
 After setup, report:
 
 1. **Live URL** (Production Publish)
-2. **Publish health:** Framework = Other; Output ≠ `public`; `GET /status` → JSON; `GET /` OK
+2. **Publish health:** Framework = Other; Output �?`public`; `GET /status` �?JSON; `GET /` OK
 3. **Preview note:** Next proxy shell used / not needed
-4. **Env Vars set** (names only — never values); note which were auto-set (`TOMORROWOS_STORE`, `DATABASE_SSL`)
+4. **Env Vars set** (names only �?never values); note which were auto-set (`TOMORROWOS_STORE`, `DATABASE_SSL`)
 5. **Store:** Supabase pooler / Neon pooled / SQLite (with warning)
 6. **Media:** Cloudinary, Vercel Blob, or local (with warning)
 7. **Brand:** name + `hostingTarget: vercel` (+ note if derived from website URL)
-8. **Runtime split:** Preview = … ; Publish = Node TomorrowOS (confirm **not** Next)
+8. **Runtime split:** Preview = �?; Publish = Node TomorrowOS (confirm **not** Next)
 9. **Open action:** if Database still ERROR, paste the pooler instruction again
 
 Protocol complete when:
@@ -1009,4 +1009,4 @@ Protocol complete when:
 - **Publish** returns Control Panel at `/` **and** `/status` JSON from pure Node `TomorrowOS.listen` with Fluid (not static `public/`, not `404: NOT_FOUND`, not `Unexpected token 'T'`), **and**
 - Q1–Q3 configuration is saved
 
-— even if a sandbox DB probe still flakes **after** the pooled URL is correctly set for Production.
+�?even if a sandbox DB probe still flakes **after** the pooled URL is correctly set for Production.