@tomorrowos/sdk 0.9.46 → 0.9.50

package/LOVABLE_SETUP.md

@@ -347,7 +347,7 @@ Copy the same keys to the **Node host** env.
     "start": "tsx server.ts"
   },
   "dependencies": {
-    "@tomorrowos/sdk": "^0.9.44",
+    "@tomorrowos/sdk": "^0.9.50",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   }

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.44+)  
+> **Protocol:** `vercel-questions/1.0` (pairs with `VERCEL_SETUP.md` 1.9+ / `@tomorrowos/sdk` 0.9.50+)  
 > **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 閳ユ窂lob recommended閳? no 閳ユ竸isable 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.44+** (`templates/cms-starter-v0`, Fluid Functions WebSockets).
+> Protocol id: `vercel-setup/1.9` — pairs with `@tomorrowos/sdk` **0.9.50+** (`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/dist/tomorrowos.d.ts

@@ -149,8 +149,8 @@ export declare class TomorrowOS extends EventEmitter {
         pushed: boolean;
     }>;
     /**
-     * Clear the daily on/off timer. The player keeps its current mute / power-save
-     * state until a new timer is set.
+     * Clear the daily on/off timer and push null to the device.
+     * Connected players drop the schedule and turn the screen back on.
      */
     clearDeviceOnOffTimer(deviceId: string): Promise<{
         deviceId: string;

package/dist/tomorrowos.js

@@ -475,8 +475,8 @@ export class TomorrowOS extends EventEmitter {
         return { deviceId: id, onOffTimer, pushed };
     }
     /**
-     * Clear the daily on/off timer. The player keeps its current mute / power-save
-     * state until a new timer is set.
+     * Clear the daily on/off timer and push null to the device.
+     * Connected players drop the schedule and turn the screen back on.
      */
     async clearDeviceOnOffTimer(deviceId) {
         const id = String(deviceId || "").trim();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tomorrowos/sdk",
-  "version": "0.9.46",
+  "version": "0.9.50",
   "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.9.44",
+  "version": "0.9.50",
   "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.9.44",
+    "@tomorrowos/sdk": "^0.9.50",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   },

package/templates/cms-starter/public/index.html

@@ -187,7 +187,7 @@
         <h2>On / off timer</h2>
         <p class="hint" id="onOffTimerModalHint">
           Daily on/off times follow the device clock. Off blacks the screen; the player stays powered and connected to the CMS.
-          Removing the timer stops the schedule and leaves the screen in its current on or off state until you set a timer again.
+          Removing the timer clears the schedule and turns the screen back on.
         </p>
         <div class="on-off-timer-grid">
           <label class="field-label">

package/templates/cms-starter/public/methods.js

@@ -1999,7 +1999,7 @@ async function removeOnOffTimerModal() {
 
   if (
     !confirm(
-      "Remove the on/off timer? The screen will stay in its current on or off state until you set a timer again."
+      "Remove the on/off timer? The schedule will be cleared and the screen will turn back on."
     )
   ) {
     return;

package/templates/cms-starter-v0/cms-panel/index.html

@@ -187,7 +187,7 @@
         <h2>On / off timer</h2>
         <p class="hint" id="onOffTimerModalHint">
           Daily on/off times follow the device clock. Off blacks the screen; the player stays powered and connected to the CMS.
-          Removing the timer stops the schedule and leaves the screen in its current on or off state until you set a timer again.
+          Removing the timer clears the schedule and turns the screen back on.
         </p>
         <div class="on-off-timer-grid">
           <label class="field-label">

package/templates/cms-starter-v0/cms-panel/methods.js

@@ -2000,7 +2000,7 @@ async function removeOnOffTimerModal() {
 
   if (
     !confirm(
-      "Remove the on/off timer? The screen will stay in its current on or off state until you set a timer again."
+      "Remove the on/off timer? The schedule will be cleared and the screen will turn back on."
     )
   ) {
     return;

package/templates/cms-starter-v0/package.json

@@ -1,6 +1,6 @@
 {
   "name": "my-cms",
-  "version": "0.9.44",
+  "version": "0.9.50",
   "description": "TomorrowOS CMS for Vercel / v0 Publish (Fluid Function + WebSockets + optional Next Preview).",
   "private": true,
   "type": "module",
@@ -17,7 +17,7 @@
     "build-player": "tomorrowos build --platform tizen"
   },
   "dependencies": {
-    "@tomorrowos/sdk": "^0.9.44",
+    "@tomorrowos/sdk": "^0.9.50",
     "dotenv": "^17.2.3",
     "tsx": "^4.19.0"
   },