@okostream/mcp 0.12.16 → 0.13.0

package/dist/server.js

@@ -116291,7 +116291,7 @@ function sanitizeScopes(scopes) {
 }
 
 // build/version.js
-var OKO_MCP_VERSION = "0.12.16";
+var OKO_MCP_VERSION = "0.13.0";
 
 // build/auth.js
 var state = null;
@@ -118496,7 +118496,15 @@ function buildCreateWebinarDocument(input) {
       description: input.description
     },
     blocks: {
-      chat: { enabled: input.chatEnabled, visibility: "always" },
+      // Starting state closed, session triggers off (owner decision 10.09):
+      // the chat exists, and the organizer opens it in analytics.
+      chat: {
+        enabled: input.chatEnabled,
+        visibility: "always",
+        intake: "closed",
+        openOnSessionStart: false,
+        closeOnSessionEnd: false
+      },
       promoBanner: { enabled: false, text: "", link: "", visibility: "always" }
     }
   };
@@ -118812,7 +118820,7 @@ function registerEventTools(server2) {
       returns: "event document fields plus id and public event URL. The event's access composition (the historical uid arrays) is never returned; ask oko_list_workspace_access for who has access.",
       examples: ["Use after oko_create_webinar to verify setup and return the event URL to the user."],
       notes: [
-        "blocks.chat: the panel exists exactly when blocks.chat.enabled is true. blocks.chat.intake says whether it ACCEPTS MESSAGES before anyone touches the live control \u2014 closed (default), open, schedule (at the event time), or session (while an analytics session runs); oko_set_chat_mode overrides it live. blocks.chat.mode and blocks.chat.visibility are legacy and read by nobody \u2014 ignore those two."
+        "blocks.chat: the panel exists exactly when blocks.chat.enabled is true (false HIDES the panel; messages are kept for 90 days and come back when it is enabled again). Message intake is ONE live state \u2014 oko_set_chat_mode reads and writes it; blocks.chat.intake is only the STARTING state an untouched event has (closed by default, or open), and blocks.chat.openOnSessionStart / closeOnSessionEnd are two triggers that flip that same state when an analytics session starts or ends. blocks.chat.mode and blocks.chat.visibility are legacy and read by nobody \u2014 ignore those two."
       ]
     }),
     inputSchema: { eventId: eventIdField },
@@ -118857,7 +118865,7 @@ function registerEventTools(server2) {
         "workspaceId: optional workspace id; omitted means personal workspace.",
         "videoUrl: optional iframe/source/player URL; normalized by OKO.",
         "eventDate: optional ISO datetime.",
-        "chatEnabled: whether the chat block is on the page at creation. It does NOT open message sending: a new event starts with intake closed, so the chat is visible and silent until the organizer opens it (oko_set_chat_mode) or sets blocks.chat.intake."
+        "chatEnabled: whether the chat block is on the page at creation (default true \u2014 the chat exists practically always). It does NOT open message sending: a new event starts closed, so the chat is visible and silent until the organizer opens it (oko_set_chat_mode, or the analytics switch), sets blocks.chat.intake to open, or enables the session triggers in oko_configure_blocks."
       ],
       returns: "new event id, public event URL, and workspaceId.",
       examples: ["Use for a complete create flow, then call oko_configure_blocks and oko_get_event."],
@@ -118870,7 +118878,7 @@ function registerEventTools(server2) {
       eventDate: external_exports.string().datetime().nullable().optional().describe("Optional webinar datetime in ISO format."),
       speakerName: external_exports.string().max(160).nullable().optional().describe("Optional speaker display name."),
       description: external_exports.string().max(3e3).nullable().optional().describe('Optional event description shown under the speaker name. Omit or pass "" for none; the literal text "null" is rejected.'),
-      chatEnabled: external_exports.boolean().default(false).describe("Whether the chat block is on the page at creation; message sending stays closed until opened.")
+      chatEnabled: external_exports.boolean().default(true).describe("Whether the chat block is on the page at creation (default true); message sending stays closed until opened.")
     },
     outputSchema: createWebinarOutputSchema,
     annotations: writeTool
@@ -118984,7 +118992,7 @@ function registerEventTools(server2) {
       returns: "event id and the list of Firestore fields updated.",
       examples: ["Use after oko_create_webinar to enable chat, bind a CTA/form, and configure other audience blocks."],
       notes: [
-        '\u{1F534} "Turn off the chat" is ambiguous, and the two meanings are not close. chat.enabled=false REMOVES the chat block from the page together with every message people wrote \u2014 irreversible for the audience, and almost never what someone asks for mid-webinar. Stopping new messages is a different tool: oko_set_chat_mode with mode="off" leaves the block and the whole history in place. When the organizer says "turn off the chat", "close the chat", "stop the chat", "disable chat", assume they mean the mode, and ASK before removing the block. The same trap in reverse: "turn the chat back on" after a pause means mode="public", not this field.',
+        '\u{1F534} "Turn off the chat" is ambiguous, and the two meanings are different actions. chat.enabled=false HIDES the chat panel from the page for everyone \u2014 the history is not deleted (messages are kept for 90 days) and comes back when the block is enabled again \u2014 but during or after a webinar that is almost never what is asked for. Stopping new messages is a different tool: oko_set_chat_mode with mode="off" leaves the panel and the history on the page and only closes the input. When the organizer says "turn off the chat", "close the chat", "stop the chat", "mute the chat", "disable chat", assume they mean CLOSING INTAKE (oko_set_chat_mode off), and ask before hiding the panel. The same trap in reverse: "turn the chat back on" after a pause means mode="public", not this field.',
         "A block toggle and its image are independent: enabling a block here works with an image already uploaded via oko_upload_image, and uploading an image never enables the block by itself.",
         "promoBanner has no text field by design: the banner is image+link. blocks.promoBanner.text seen in event documents is legacy and is never rendered on the event page.",
         'videoPlaceholder.enabled only allows the placeholder; viewers see it after oko_set_block_visibility with block "placeholder" and visible true (a live override, stored outside the event document). Chat, CTA, banner and cards appear as soon as they are enabled here.',
@@ -118996,8 +119004,10 @@ function registerEventTools(server2) {
     inputSchema: {
       eventId: eventIdField,
       chat: external_exports.object({
-        enabled: external_exports.boolean().optional().describe("Whether the chat block is ON THE PAGE. false removes it together with the message history \u2014 see the note above before using it."),
-        intake: external_exports.enum(["closed", "open", "schedule", "session"]).optional().describe("When the chat starts accepting messages before any live override: closed (default \u2014 visible and silent until opened), open, schedule (at the event time), session (while an analytics session runs)."),
+        enabled: external_exports.boolean().optional().describe("Whether the chat panel is ON THE PAGE. false hides it for everyone (history kept for 90 days, back when re-enabled) \u2014 see the note above: to stop new messages use oko_set_chat_mode instead."),
+        intake: external_exports.enum(["closed", "open"]).optional().describe("STARTING state of message intake \u2014 what the chat does while nobody has touched the live control: closed (default \u2014 on the page, history visible, input closed) or open. The live control (oko_set_chat_mode) is the state itself; this field does not override it."),
+        openOnSessionStart: external_exports.boolean().optional().describe("Session trigger: open message intake when an analytics session starts (default false)."),
+        closeOnSessionEnd: external_exports.boolean().optional().describe("Session trigger: close message intake when the analytics session ends (default false)."),
         visibility: external_exports.enum(["always", "hidden"]).optional()
       }).optional(),
       promoBanner: external_exports.object({ enabled: external_exports.boolean().optional(), link: external_exports.string().max(1e3).optional(), visibility: external_exports.enum(["always", "hidden"]).optional(), formId: external_exports.string().nullable().optional() }).optional(),
@@ -119020,6 +119030,10 @@ function registerEventTools(server2) {
       patch["blocks.chat.enabled"] = args.chat.enabled;
     if (args.chat?.intake !== void 0)
       patch["blocks.chat.intake"] = args.chat.intake;
+    if (args.chat?.openOnSessionStart !== void 0)
+      patch["blocks.chat.openOnSessionStart"] = args.chat.openOnSessionStart;
+    if (args.chat?.closeOnSessionEnd !== void 0)
+      patch["blocks.chat.closeOnSessionEnd"] = args.chat.closeOnSessionEnd;
     if (args.chat?.visibility !== void 0)
       patch["blocks.chat.visibility"] = args.chat.visibility;
     if (args.promoBanner?.enabled !== void 0)
@@ -119079,10 +119093,10 @@ function registerEventTools(server2) {
       hints.push("blocks.chat.visibility was stored but the event page does not read it: the chat panel exists exactly when blocks.chat.enabled is true, and sending is opened or closed live with oko_set_chat_mode. Drop the field.");
     }
     if (args.chat?.enabled === false) {
-      hints.push('The chat block is now off in setup: it is gone from the page for everyone, together with every message the audience wrote. If the goal was only to stop NEW messages \u2014 which is what "turn off the chat" usually means during or after a webinar \u2014 re-enable it here and use oko_set_chat_mode with mode "off" instead: the block and the whole history stay in place. Worth confirming with the organizer which of the two they meant.');
+      hints.push('The chat panel is now hidden from the page for everyone. Nothing was deleted: messages are kept for 90 days and come back when the block is enabled again. If the goal was only to stop NEW messages \u2014 which is what "turn off the chat" usually means during or after a webinar \u2014 re-enable the block here and use oko_set_chat_mode with mode "off" instead: the panel and the history stay visible, only the input closes. Worth confirming with the organizer which of the two they meant.');
     }
     if (args.chat?.enabled === true && args.chat?.intake === void 0) {
-      hints.push('The chat block is on the page, but message sending stays closed until it is opened: a chat nobody opened is silent by default. Open it now with oko_set_chat_mode mode "public", or set blocks.chat.intake to open / schedule / session so it opens by itself.');
+      hints.push('The chat block is on the page, but message intake stays closed until it is opened: a chat nobody opened is silent by default. Open it now with oko_set_chat_mode mode "public", set blocks.chat.intake to "open" so new events of this kind start open, or enable openOnSessionStart / closeOnSessionEnd so the analytics session opens and closes it by itself.');
     }
     const currentBlocks = current.blocks && typeof current.blocks === "object" ? current.blocks : {};
     const bannerHasImage = Boolean(safeString(currentBlocks.promoBanner?.imageUrl) || safeString(currentBlocks.promoBanner?.imageMasterUrl));
@@ -119900,7 +119914,7 @@ function registerLiveTools(server2) {
     description: toolDescription({
       summary: "Read main RTDB live controls, aggregate analytics, and chat settings for an event.",
       args: ["eventId: event to inspect."],
-      returns: "eventId, agg metrics, ctrl live overrides, and chat settings (mode, slowModeMs, automodEnabled, allowViewerLinks).",
+      returns: "eventId, agg metrics, ctrl live overrides, and chat settings (mode, slowModeMs, automodEnabled, allowViewerLinks, plus accepting \u2014 whether message intake is open right now, as the server enforces it).",
       examples: ["Use during a webinar before changing live block visibility or starting/ending sessions."],
       notes: [
         "Live state does not carry the event team: to see who has access to an event and with which permissions, use oko_list_workspace_access on the event's workspace."
@@ -119923,6 +119937,7 @@ function registerLiveTools(server2) {
       if (value !== null && value !== void 0)
         chat[field2] = value;
     });
+    chat.accepting = chat.mode !== "off";
     return textResult({ eventId, agg: aggSnap.val() ?? {}, ctrl: ctrlSnap.val() ?? {}, chat });
   });
   server2.registerTool("oko_set_block_visibility", {
@@ -120055,13 +120070,13 @@ function registerLiveTools(server2) {
       exampleCall: { "eventId": "Kx9pQ2mR7tL4vB8nW3cY", "mode": "off", "confirm": true },
       args: [
         "eventId: event to control.",
-        "mode: public (anyone can send), off (input closed, history stays visible), or null to fall back to the event's own setting (blocks.chat.intake, closed unless the organizer chose otherwise).",
+        "mode: public (anyone can send), off (input closed, history stays visible), or null to clear the live control so the event's STARTING state applies (blocks.chat.intake \u2014 closed unless the organizer chose open). Message intake is one live state; this tool, the analytics switch and the session triggers all write it.",
         "confirm: must be true."
       ],
       returns: "eventId and the effective chat mode.",
       examples: ['Use mode="off" to pause a chat storm; use mode="public" to reopen.'],
       notes: [
-        '\u{1F534} "Turn off the chat" means one of TWO different things, and picking the wrong one destroys what people wrote. THIS tool stops new messages: the block stays on the page, history stays readable, nothing is lost. The other one \u2014 oko_configure_blocks with chat.enabled=false \u2014 removes the block from the page together with the whole conversation. When the organizer says "turn off the chat", "close the chat", "stop the chat", "mute the chat" during or after a webinar, they almost always mean THIS tool. Ask before removing the block.',
+        '\u{1F534} "Turn off the chat" means one of TWO different things. THIS tool stops new messages: the panel stays on the page, history stays readable, nothing changes for the audience except the input. The other one \u2014 oko_configure_blocks with chat.enabled=false \u2014 HIDES the whole panel (history is kept for 90 days and returns when re-enabled), which is a page-layout decision, not a live-show one. When the organizer says "turn off the chat", "close the chat", "stop the chat", "mute the chat", "disable chat" during or after a webinar, they almost always mean THIS tool. Ask before hiding the panel.',
         'This is the full replacement for the legacy pause via oko_set_block_visibility(block="chat"): prefer oko_set_chat_mode.',
         "There are no other levels: the server has exactly two states, sending open or closed. History is always visible; the mode never restricts who can read or hides anyone's messages."
       ]
@@ -120071,7 +120086,7 @@ function registerLiveTools(server2) {
       // LD5a-2 / A8 (owner decision 03.09): "auth" and "owner" were promised
       // here and enforced nowhere — the rule and every client only check
       // `mode !== "off"`. The contract now says what the server does.
-      mode: external_exports.enum(["public", "off"]).nullable().describe("Chat mode: public or off; null drops the live override and falls back to the event setting."),
+      mode: external_exports.enum(["public", "off"]).nullable().describe("Chat mode: public or off; null clears the live control so the event's starting state (blocks.chat.intake) applies."),
       confirm: external_exports.boolean().optional().describe("Required true to change the live chat mode.")
     },
     outputSchema: basicEventOutputSchema,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@okostream/mcp",
-  "version": "0.12.16",
+  "version": "0.13.0",
   "description": "Control OKO Stream webinars from Claude, Codex, and other MCP clients.",
   "license": "UNLICENSED",
   "author": {