@voxevolv/client 0.3.1 → 0.3.2

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to `@voxevolv/client` are recorded here.
 
+## 0.3.2 - 2026-09-17
+
+- Recover from agent loss even while the room remains connected, with a default three-minute recovery deadline.
+- Restore the client handshake, tools, audio, and latest replacement context before reporting connected.
+- Coalesce pending replacement context by key; superseded pending requests reject explicitly.
+- Expose `autoRejoin.timeoutMs`; explicit `maxAttempts` remains an optional earlier limit.
+
 ## 0.3.1 - 2026-07-28
 
 - Treat a server-pushed `session.ending` event as a graceful hang-up: it marks

package/README.md

@@ -26,7 +26,7 @@ Browsers without a build step can use the versioned bundle after publication:
 ```html
 <script type="module">
   import { RealtimeSession } from
-    "https://cdn.jsdelivr.net/npm/@voxevolv/client@0.3.1/dist/browser/index.js";
+    "https://cdn.jsdelivr.net/npm/@voxevolv/client@0.3.2/dist/browser/index.js";
 </script>
 ```
 
@@ -125,12 +125,41 @@ await session.connect({ waitForRemoteAudio: false });
 
 ## Recovery, rejoin, and connection quality
 
-Set `autoRejoin: true` to let the SDK own recovery after LiveKit exhausts its
-transport-level reconnect. Automatic recovery runs only after the session has
+With `@voxevolv/client@0.3.2`, set `autoRejoin: true` to let the SDK recover
+when an agent leaves, its worker changes, a context command times out, or LiveKit
+exhausts its transport reconnect. Automatic recovery runs only after the session has
 connected successfully, never after an explicit `disconnect()`, `end()`, or
 terminal LiveKit removal. It waits for browser connectivity, obtains a fresh
 room token, and retries with bounded backoff.
 
+Automatic rejoin has a default 180-second deadline, including time spent offline.
+Use `autoRejoin: { timeoutMs: 180_000 }` to configure it; an explicit `maxAttempts`
+can stop retries earlier. This renews the room connection for the **same session**.
+It never creates a replacement assessment/session. `connected` is reported only
+after the client hello (including tool handlers), agent readiness, remote audio
+(unless opted out), and replacement-context restoration succeed.
+
+The updated server protects replacement-worker startup with a three-minute
+participant grace period. It restores up to the latest 200 committed transcript
+messages within 100,000 UTF-8 bytes and skips the initial greeting on resume.
+Uncommitted speech, raw audio, provider-internal state, and tool executions are
+not replayed. Recovery does not extend an application's timer or the session's
+configured maximum duration.
+
+Use stable keys and `mode: "replace"` for screen frames and timer snapshots.
+Only one update per key is sent at a time; while recovering, the newest pending
+value replaces older pending values. Superseded callers reject with
+`Context update superseded by a newer value`, so handle each returned promise.
+The SDK retains up to 64 keys / 16 MiB of recent replacement context for recovery;
+it restores accepted values with `respond: false`. Append updates are not queued
+or replayed during recovery because repeating them could duplicate input. Updates
+already in flight may have reached the server even if their acknowledgment was lost.
+
+Keep the existing `RealtimeSession` instance during recovery, register tools on
+that instance, and use `onStateChange` / `onRecovery` for UI. Avoid application
+retry loops that create new sessions. Older clients remain API-compatible but
+need the SDK upgrade to gain agent-loss detection and context restoration.
+
 ```ts
 session.onStateChange((state) => {
   // reconnecting: LiveKit is restoring transport