@voxevolv/client 0.3.10 → 0.3.12

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 All notable changes to `@voxevolv/client` are recorded here.
 
+## 0.3.12 - 2026-10-04
+
+- Let native LiveKit reconnect finish without treating participant cleanup as an
+  agent departure and starting a second reconnect. Genuine departures still recover.
+- During recovery, abandon a handshake when queued reliable data stops draining
+  for five seconds. Initial joins and slow but draining channels retain their
+  existing handshake deadline. Cancellation stops the recovery watchdog.
+- Record recovery stage timings, token HTTP failures/timeouts, and completion
+  through agent readiness and requested remote audio. Deploy the control API's
+  expanded diagnostic allowlist before upgrading browser consumers; no migration
+  is required.
+
+## 0.3.11 - 2026-10-01
+
+- Fix screenshot uploads causing browser-tool acknowledgements to be discarded
+  out of sequence. The packaged LiveKit 2.20.0 runtime assigns reliable packet
+  sequence numbers after waiting for buffer space, without adding a send queue
+  or changing buffer limits. Both npm and standalone browser builds include the fix.
+
 ## 0.3.10 - 2026-09-29
 
 - Add browser tool RPC diagnostics with call IDs, handler stages, timing, and

package/README.md

@@ -15,6 +15,13 @@ into `dist/`. It also emits a self-contained browser bundle at
 integrity value is written to `dist/browser/index.js.sha384` and
 `dist/browser/manifest.json`.
 
+Both runtime entry points use a packaged LiveKit 2.20.0 correction for reliable
+packet ordering during simultaneous image uploads and browser tool replies.
+The build applies `scripts/livekit-sequence-patch.mjs` to a copy in `dist/vendor/`;
+it does not modify installed dependencies or require consumer install scripts.
+Review the patch and run the reliable-sequence tests when upgrading LiveKit.
+The correction changes sequence assignment timing, not buffer limits or retries.
+
 Bundlers should use the package export:
 
 ```ts