@burdenoff/website-sdk 2026.1105.2 → 2026.1105.3

package/README.md

@@ -420,6 +420,60 @@ publishes audio, video or data, and it sends the avatar nothing to say.
   site's main bundle and the view's chunk carry none of it. On alpha, a browser
   WebSocket cannot carry Cloudflare Access service-token headers, so the
   stream needs the Access cookie for the gateway host.
+- **The mic through the browser's own speech recognition (BOFF-9797 Stage C,
+  the operator's decision of 2026-11-05, dark).** The same `mic: true` opt-in
+  (default unset: no mic); the server's availability decides how the mic works.
+  Where the last `ok` answer carries `mic: {"mode": "browser",
+  "maxPressSeconds": 30}` (contract v1.6, the avatar service's
+  `AVATAR_WEB_MIC=browser`; read strictly: any other value is `unreadable` and
+  means no mic) and the consent version's words describe it (the new
+  `AvatarConsentCopy.micNotice`), the mic uses `SpeechRecognition` /
+  `webkitSpeechRecognition`, as the product assistant does: the browser's own
+  speech service turns the voice into text, and **nothing of a press reaches
+  our server**; the text goes into the box and leaves only on Send. Offered
+  only in a secure context with a recognizer, and never in Firefox (`Firefox/`,
+  `FxiOS/`: desktop Firefox gains an on-device recognizer in release 160) or
+  Brave (`navigator.brave`: no speech service behind its recognizer). The
+  gateway's stream is never offered beside a `mic` the server sent (readable or
+  not), nor under words that name a `micNotice`; without a `mic` it is offered
+  exactly as before. The first tap shows the notice the words name,
+  `web-mic-2026-11-21-c` (714 bytes, SHA-256 `0a15bf5d…8e06de8f`); agreement is
+  kept per notice version, so another version is shown again. Two new consent
+  versions, DRAFTS for the privacy review that no server names yet:
+  `web-consent-2026-11-21-c` (bot check `turnstile`, 1,761 bytes, SHA-256
+  `824f389a…111790db`) and `web-consent-2026-11-22-c` (bot check `off`, 1,717
+  bytes, SHA-256 `d84a038b…1eb6200c`), Stage D's words with the mic's sentences
+  added. Tap to start, tap to stop on every platform: the recognizer
+  (`en-IN`, one `en-US` retry on `language-not-supported`, interim results,
+  `continuous` except on a touch device) starts inside the tap where the
+  browser reports the microphone granted; otherwise the tap first opens the
+  microphone and releases it at once (`getUserMedia`, nothing kept or sent),
+  which is what raises the permission prompt on Android Chrome and iOS, and
+  the recognizer starts 250 ms later (the Chat dictation's mobile handling,
+  `use-speech-input`). The 30 s limit counts from its `onstart`, and an engine
+  that ends by itself (a pause, a phone's single utterance, `no-speech`) is
+  replaced in the same press, its words joined: at once on a computer, after
+  120 ms on a touch device, after a 2 s cooldown after a throw (or, on a
+  computer, an instant end); only 8 instant ends in a row, or 60 recognizers
+  in all, end a press by itself. The last words after `stop()` are waited for
+  (3 s), and a tap meanwhile does nothing. A refused microphone
+  (`NotAllowedError`, or `not-allowed` where the microphone was not
+  confirmed) says it is blocked (the mic stays); a refusal right after a grant
+  is retried once after 350 ms; refused again, or `service-not-allowed`,
+  `audio-capture`, no microphone, or a second `network` in a row, it says it
+  can't be used here and goes for the page. Words heard before any failure are
+  kept. Inside a Stage D session a tap while the avatar speaks sends
+  `interrupt`, recording sends `listening` marks from `onstart`, never within
+  5 s of the one before (at most 12 a minute, within the session's 30 turns a
+  minute); the mic goes the moment a question is sent and is back once its
+  answer has gone to the session, so the avatar never starts an answer into
+  an open microphone (a tap while it speaks sends `interrupt` first; how fast
+  the cut lands, and whether to mute the avatar locally on that tap, are open
+  Stage D items). What is heard and the box carry rrweb's `rr-block`/`rr-mask` (the box also `rr-ignore`), so a site's
+  session replay records none of it before Send, and nothing in the mic calls
+  the site's analytics. **Before alpha is switched on:** each of the four sites'
+  session replay must be off, or honour those classes, and each privacy notice
+  (`/privacy#live-avatar`) needs its microphone paragraph.
 - **The answers after the first (BOFF-9797 Stage D, dark).** Only where the
   create's 201 carries `followUps: {maxAnswers, idleSeconds,
   maxAnswerWaitSeconds}` (the avatar service adds it only under its

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

@@ -1,6 +1,6 @@
 import * as react from 'react';
 import { ReactNode } from 'react';
-import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-BL8FTm0I.mjs';
+import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-BxiE66Im.mjs';
 import '../types-CTUJNvQu.mjs';
 import '../use-explore-chat-CbfohA9O.mjs';
 import '../explore-types-Ol1Mm3dW.mjs';

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

@@ -1,6 +1,6 @@
 import * as react from 'react';
 import { ReactNode } from 'react';
-import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-auLKxSzx.js';
+import { E as ExplorePanelAvatarLive, a as ExploreLocale, A as AvatarConversation } from '../explore-avatar-live-config-1zeXdMer.js';
 import '../types-CTUJNvQu.js';
 import '../use-explore-chat-B3dOOvJN.js';
 import '../explore-types-Ol1Mm3dW.js';