@burdenoff/website-sdk 2026.1102.2 → 2026.1104.1

package/README.md

@@ -320,7 +320,7 @@ publishes audio, video or data, and it sends the avatar nothing to say.
   what the Avatar view shows until it arrives (the same picture, and the same
   bytes in a server render or a prerendered page, as before). A site that never
   passes `avatar.live` never downloads it: its bundle grows by under a kilobyte
-  gzipped, instead of the roughly twelve the view weighs. Your bundler needs
+  gzipped, instead of the roughly twenty-five the view weighs. Your bundler needs
   to split dynamic imports, as Vite, webpack and Rollup do. If the file cannot
   be fetched (offline, or a deploy has replaced it), or has not arrived after
   eight seconds, the Avatar view shows what it showed before the live avatar,
@@ -358,6 +358,36 @@ publishes audio, video or data, and it sends the avatar nothing to say.
   turning the bot check on or off is a server config change: a site needs no
   new build for it, as long as its build carries a site key for `turnstile` and
   its CSP allows Cloudflare (below).
+- **The Avatar tab's own question box (web API contract v1.3, additive).** The
+  availability answer's `questions` says which first questions the server
+  reads the answer to: `"suggested"` (only the exact suggested questions, as
+  before) or `"any"` (a question the visitor typed too). A server older than
+  v1.3 sends none and is read as `suggested`; an unknown value leaves the view
+  as it was. Under `any`, and only with consent copy written for it (below),
+  the Avatar tab has a box of its own ("Ask the avatar…", at most 300
+  characters, text only, Enter to ask) and the panel's suggested questions as
+  chips. A question asked there is the first of a new chat, sent with
+  `surface: "AVATAR"` (the chat's own composer never sends a surface), and its
+  first answer is the only one the card is offered for: the card shows while
+  the answer is written, with **Start when ready**. That press is bound to this
+  conversation, its question and the answer on its way, the site, the locale,
+  the page and the consent version and bot check; any of them changing, Cancel,
+  leaving the tab, closing the panel or hiding the page calls it off with
+  nothing created. Once the answer is ready the view asks availability again
+  and checks the answer as the service will (an answer, one to sixty-four
+  references, no files, under fourteen minutes old), and creates the session
+  only if nothing differs; otherwise it shows the card for what is offered now.
+  A create is never sent again by itself. A conversation that is not a new
+  chat started in the tab (a question asked in Chat, a second question, an
+  answer too old) is never read and never reset by the tab: it offers **New
+  chat for the avatar** ("Your current chat stays in History."), and the box
+  appears after that tap. After the day's session (a `limits` refusal, or this
+  browser's own note of a session today, kept in `localStorage` as
+  `boff.explore.avatarUsedOn`), the box asks ordinary questions, without
+  `surface`, and the answer shows in the tab as text, with "Read the answer and
+  sources in Chat". Pass `currentPath` to `ExplorePanel` (as
+  `SiteAssistantDock` does) so a page change calls off a "Start when ready"
+  at once; without it, the window's path is checked before the create.
 - **One answer: the first, to a suggested question.** The avatar service
   accepts a conversation only when it holds exactly two messages: the first user
   message (a suggested question) and the first assistant answer, completed. The
@@ -390,10 +420,24 @@ publishes audio, video or data, and it sends the avatar nothing to say.
   limits, region, language, paused, a question the avatar cannot read) is one
   short sentence and "Continue in Chat". A network or CORS failure, or a route
   that is not there, shows the view as it was before.
-- **Ending.** Stop, switching to Chat, closing the panel, hiding the page, and
-  the live avatar going off under a session (the panel's locale changing to one
+- **Ending.** Stop, closing the panel, leaving the page (`pagehide`), and the
+  live avatar going off under a session (the panel's locale changing to one
   whose strings have not been reviewed) all end the session with a `keepalive`
-  request and leave the room. The end is a simple CORS request: its body is a
+  request and leave the room. Once the create has been sent (connecting,
+  joining, speaking), switching to the Chat tab (or pressing Continue in Chat)
+  and hiding the page (another browser tab, another app) do **not** end it: the
+  Avatar pane is only hidden, the room's video and audio stay attached, and the
+  avatar speaks to the end the server planned for it, which a hidden page
+  cannot extend. Coming back to the Avatar tab shows the session as it is, with
+  the countdown to the server's end, and asks nothing again. Before the create,
+  nothing paid exists, so the Chat tab still calls off an availability check, a
+  "Start when ready" and a bot check, and a hidden page still calls off a
+  "Start when ready" and returns a bot check to the consent card, all with
+  nothing created. While a session is created, joined or played, Chat's own
+  read-aloud and dictation are held (`ExplorePage`'s `voiceHold`): a reading
+  under way stops, and both controls stay where they are, `aria-disabled`, with
+  the avatar's status line as their title, until the session ends; nothing in
+  Chat ends the session. The end is a simple CORS request: its body is a
   string and the SDK sets no `content-type`, so the browser sends it as
   `text/plain;charset=UTF-8` (which the gateway accepts for this route), and on
   production nothing else is added, so no preflight has to complete while the
@@ -416,7 +460,16 @@ publishes audio, video or data, and it sends the avatar nothing to say.
   version that says so, or the view stays as it was.
   `web-consent-2026-10-31` (which names the product, "a suggested Healthy Bowl
   question") and `web-consent-2026-11` stay, unchanged, for servers that still
-  name them.
+  name them. Each version also says which questions its words describe, and the
+  card is shown only where the server's `questions` is the same.
+  `web-consent-2026-11-05` (bot check `turnstile`, 904 bytes, SHA-256
+  `75e7e6e84d68bba35ccb208151e2e9e20c69efac2896b17b1d2f1cda46d0bb9f`) and
+  `web-consent-2026-11-06` (bot check `off`, 860 bytes, SHA-256
+  `f5a673f6c325fe2032f59a561169f5ad8b8598d615e78abbe7b65314e4e6f7bd`) are the
+  versions for `questions: "any"`: the avatar reads "the first answer in a new
+  chat started in the Avatar tab, provided it passes the speech checks, whether
+  you chose a suggested question or typed your own", and the visitor is told
+  not to put personal details in a typed question.
 - **How a session ended.** When the worker leaves, the server closes the room,
   or the session's time runs out with the room still open, the view says only
   "The live avatar has ended." (key `finished`). The browser
@@ -471,9 +524,11 @@ publishes audio, video or data, and it sends the avatar nothing to say.
     of the same host for the validation check.
 - **Not verified in this package.** Every test here uses fakes: nothing reaches
   Turnstile, the gateway, the avatar service or the media room. Left to the
-  alpha test: real playback on iPhone Safari and Android Chrome; that
-  `page_hide` ends actually arrive from those browsers; and that the receive-only
-  token has `canPublish=false` and `canPublishData=false`, and a worker RPC
+  alpha test: real playback on iPhone Safari and Android Chrome; that the voice
+  keeps playing behind the Chat tab and in a background browser tab there (a
+  browser may suspend it; the server still ends the session at its planned
+  end); that `page_hide` ends actually arrive from those browsers; and that the
+  receive-only token has `canPublish=false` and `canPublishData=false`, and a worker RPC
   addressed to the viewer is dropped without disconnecting it (the media client
   answers incoming RPC requests on its own, so "never publishes" holds only as
   far as the token's permissions do).

package/dist/avatar-live-view/index.d.mts

@@ -1,14 +1,19 @@
 import * as react from 'react';
 import { ReactNode } from 'react';
-import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-Bp3kQbU2.mjs';
+import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-N4WhJzgS.mjs';
 import '../types-CndbmBK-.mjs';
-import '../use-explore-chat-zRuoAin6.mjs';
-import '../explore-types-Bb2Ih3d8.mjs';
+import '../use-explore-chat-CbfohA9O.mjs';
+import '../explore-types-Ol1Mm3dW.mjs';
 
 interface AvatarLiveViewProps {
     live: ExplorePanelAvatarLive;
     /** The Avatar view is showing: the panel is open and its Avatar tab is selected. */
     active: boolean;
+    /**
+     * The panel is open, whichever tab it shows. With `active` it tells the Chat tab (open, not active: the pane is only
+     * hidden, and a session under way keeps playing) from the panel closing (not open: what is under way ends).
+     */
+    open: boolean;
     locale: ExploreLocale;
     /** The product the panel speaks for, when it is one product's own; null on the portfolio's. */
     productName: string | null;
@@ -19,8 +24,18 @@ interface AvatarLiveViewProps {
     };
     /** The Avatar tab as it was before the live avatar: shown whenever the live avatar is not offered or not reachable. */
     fallback: ReactNode;
-    /** Back to the Chat tab. Leaving the Avatar tab ends a session, like any other way out of it. */
+    /**
+     * Back to the Chat tab. Like the Chat tab itself, it calls off a start that has not been sent yet, and leaves a
+     * session under way speaking.
+     */
     onContinueInChat: () => void;
+    /**
+     * Told whenever the avatar's voice starts or stops being the page's: its status line while a session is being
+     * created, joined or played ("Connecting to the live avatar…", "The avatar is speaking."), and null otherwise (and
+     * when the view goes). The panel holds Chat's own read-aloud and dictation meanwhile, so the page never speaks in two
+     * voices and the microphone never takes down the avatar's.
+     */
+    onVoiceHold?: (line: string | null) => void;
     /** "Continue in Chat" in the panel's language: the panel's own word for it, so this chunk carries none of the panel's. */
     continueInChat: string;
     /**
@@ -28,6 +43,15 @@ interface AvatarLiveViewProps {
      * `reset`, as the chat's own New chat button does, then the Chat tab) where this conversation can never be read.
      */
     newChat: string;
+    /** "Send" and "Try asking" in the panel's language, for the Avatar tab's own question box. */
+    send: string;
+    tryAsking: string;
+    /** The suggested questions the chat view shows: the box's chips. */
+    prompts: readonly string[];
+    /** No precise pointer: the box is not focused by itself, so the keyboard does not cover the view. */
+    touchFirst: boolean;
+    /** The host router's path, when it has one: a "Start when ready" is called off when it changes. */
+    currentPath: string | undefined;
     /**
      * Nothing to ask the server about: an incomplete config, no gateway, no shared conversation to read (no provider, or a
      * read-only shared one), or a locale whose strings have not been reviewed. The tab stays as it was. Decided by
@@ -42,6 +66,6 @@ interface AvatarLiveViewProps {
     /** The panel's conversation, null when there is no provider. */
     conversation: AvatarConversation | null;
 }
-declare function AvatarLiveView({ live, active, locale, productName, still, fallback, onContinueInChat, continueInChat, newChat, off, base, headers, conversation, }: AvatarLiveViewProps): react.JSX.Element;
+declare function AvatarLiveView({ live, active, open, locale, productName, still, fallback, onContinueInChat, onVoiceHold, continueInChat, newChat, send, tryAsking, prompts, touchFirst, currentPath, off, base, headers, conversation, }: AvatarLiveViewProps): react.JSX.Element;
 
 export { AvatarLiveView, type AvatarLiveViewProps };

package/dist/avatar-live-view/index.d.ts

@@ -1,14 +1,19 @@
 import * as react from 'react';
 import { ReactNode } from 'react';
-import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-Cetx8-Zu.js';
+import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-CAfN5eAX.js';
 import '../types-CndbmBK-.js';
-import '../use-explore-chat-DunjG-3p.js';
-import '../explore-types-Bb2Ih3d8.js';
+import '../use-explore-chat-B3dOOvJN.js';
+import '../explore-types-Ol1Mm3dW.js';
 
 interface AvatarLiveViewProps {
     live: ExplorePanelAvatarLive;
     /** The Avatar view is showing: the panel is open and its Avatar tab is selected. */
     active: boolean;
+    /**
+     * The panel is open, whichever tab it shows. With `active` it tells the Chat tab (open, not active: the pane is only
+     * hidden, and a session under way keeps playing) from the panel closing (not open: what is under way ends).
+     */
+    open: boolean;
     locale: ExploreLocale;
     /** The product the panel speaks for, when it is one product's own; null on the portfolio's. */
     productName: string | null;
@@ -19,8 +24,18 @@ interface AvatarLiveViewProps {
     };
     /** The Avatar tab as it was before the live avatar: shown whenever the live avatar is not offered or not reachable. */
     fallback: ReactNode;
-    /** Back to the Chat tab. Leaving the Avatar tab ends a session, like any other way out of it. */
+    /**
+     * Back to the Chat tab. Like the Chat tab itself, it calls off a start that has not been sent yet, and leaves a
+     * session under way speaking.
+     */
     onContinueInChat: () => void;
+    /**
+     * Told whenever the avatar's voice starts or stops being the page's: its status line while a session is being
+     * created, joined or played ("Connecting to the live avatar…", "The avatar is speaking."), and null otherwise (and
+     * when the view goes). The panel holds Chat's own read-aloud and dictation meanwhile, so the page never speaks in two
+     * voices and the microphone never takes down the avatar's.
+     */
+    onVoiceHold?: (line: string | null) => void;
     /** "Continue in Chat" in the panel's language: the panel's own word for it, so this chunk carries none of the panel's. */
     continueInChat: string;
     /**
@@ -28,6 +43,15 @@ interface AvatarLiveViewProps {
      * `reset`, as the chat's own New chat button does, then the Chat tab) where this conversation can never be read.
      */
     newChat: string;
+    /** "Send" and "Try asking" in the panel's language, for the Avatar tab's own question box. */
+    send: string;
+    tryAsking: string;
+    /** The suggested questions the chat view shows: the box's chips. */
+    prompts: readonly string[];
+    /** No precise pointer: the box is not focused by itself, so the keyboard does not cover the view. */
+    touchFirst: boolean;
+    /** The host router's path, when it has one: a "Start when ready" is called off when it changes. */
+    currentPath: string | undefined;
     /**
      * Nothing to ask the server about: an incomplete config, no gateway, no shared conversation to read (no provider, or a
      * read-only shared one), or a locale whose strings have not been reviewed. The tab stays as it was. Decided by
@@ -42,6 +66,6 @@ interface AvatarLiveViewProps {
     /** The panel's conversation, null when there is no provider. */
     conversation: AvatarConversation | null;
 }
-declare function AvatarLiveView({ live, active, locale, productName, still, fallback, onContinueInChat, continueInChat, newChat, off, base, headers, conversation, }: AvatarLiveViewProps): react.JSX.Element;
+declare function AvatarLiveView({ live, active, open, locale, productName, still, fallback, onContinueInChat, onVoiceHold, continueInChat, newChat, send, tryAsking, prompts, touchFirst, currentPath, off, base, headers, conversation, }: AvatarLiveViewProps): react.JSX.Element;
 
 export { AvatarLiveView, type AvatarLiveViewProps };