@voxevolv/client 0.3.3 → 0.3.4

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 All notable changes to `@voxevolv/client` are recorded here.
 
+## 0.3.4 - 2026-09-22
+
+- Add a typed `trigger` and safe command correlation fields to every recovery event.
+- Keep the latest 128 content-free diagnostic entries in memory and report them
+  only after a slow operation, rejection, failure, timeout, or reconnect.
+- Send triggered reports through the session-scoped diagnostics endpoint without
+  exposing context text, images, tokens, or request URLs, and never let reporting
+  failures affect the realtime call.
+- Coalesce rate-limited triggers into a trailing report and stop waiting on a
+  diagnostics request after five seconds, so later failure evidence is not lost.
+
 ## 0.3.3 - 2026-09-17
 
 - Add identified, revisioned transcript snapshots with `onTranscriptUpdated()` and `session.transcript`.

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.2/dist/browser/index.js";
+    "https://cdn.jsdelivr.net/npm/@voxevolv/client@0.3.4/dist/browser/index.js";
 </script>
 ```
 
@@ -127,7 +127,7 @@ await session.connect({ waitForRemoteAudio: false });
 
 ## Recovery, rejoin, and connection quality
 
-With `@voxevolv/client@0.3.2`, set `autoRejoin: true` to let the SDK recover
+With `@voxevolv/client@0.3.2` or newer, 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
@@ -169,8 +169,17 @@ session.onStateChange((state) => {
   renderConnectionState(state);
 });
 
-session.onRecovery(({ status, strategy, attempt, error }) => {
-  recordRecovery({ status, strategy, attempt, error });
+session.onRecovery(({ status, strategy, attempt, trigger, messageId, contextKey, timeoutMs, error }) => {
+  recordRecovery({
+    status,
+    strategy,
+    attempt,
+    trigger,
+    messageId,
+    contextKey,
+    timeoutMs,
+    error,
+  });
 });
 
 session.onConnectionQuality((quality) => {
@@ -182,6 +191,17 @@ session.onConnectionQuality((quality) => {
 `waitForState(states, timeoutMs, { signal })` is available for advanced flows
 that need to await a bounded set of lifecycle states.
 
+In version 0.3.4, every recovery event includes a typed `trigger`, such as
+`context_command_timeout`, `livekit_disconnected`, `agent_disconnected`, or
+`worker_replaced`. Context timeouts also include the safe `messageId`,
+`contextKey`, and `timeoutMs` correlation fields. The SDK keeps the latest 128
+content-free transport and command entries in memory. It sends a throttled,
+best-effort report only after a slow operation, rejection, failure, timeout, or
+reconnect. Reports never include context text, screenshots, tokens, or raw URLs,
+and reporting failures never affect the call. A trigger received during the
+throttle window is retained for one trailing report, and each diagnostics request
+stops waiting after five seconds so a stuck endpoint cannot block later evidence.
+
 Manual `rejoin()` remains available. It obtains a fresh room token, disconnects
 any underlying room connection, and reconnects with the original microphone or
 application-owned track choice. A managed microphone that the user muted with
@@ -199,6 +219,7 @@ enabled by default), or a same-origin proxy base that forwards only:
 
 - `POST /sessions/{id}/room-tokens`
 - `GET /sessions/{id}/events`
+- `POST /sessions/{id}/diagnostics`
 - `DELETE /sessions/{id}`
 
 The proxy must forward the browser's `Authorization: Bearer vsa_...` header. It