- Playback: Fixed future Chrome recordings in cyberchat-app.js (line 865):

Records one finalized WebM instead of 250ms fragments.
Waits for final audio data before releasing the microphone.
Handles startup/finalization failures cleanly.
Bumped frontend cache version to .8.
Verified JavaScript syntax, JSON, browser rendering, and no console 
errors. Existing uploaded clips remain unchanged. A real microphone test 
wasn’t available in the browser runner.
References: MDN MediaRecorder, Chromium WebM metadata issue.

README.md

@@ -237,6 +237,8 @@ Recording selection is browser-driven:
 5. AAC
 6. Browser default MediaRecorder format
 
+The recorder collects one finalized blob at stop instead of concatenating short live WebM slices. This avoids Chrome-generated fragment metadata that other browsers may reject.
+
 When FFmpeg is disabled, the accepted browser recording is stored unchanged. WebM remains the preferred default when the browser supports it. Safari and iPhone can upload MP4/AAC directly.
 
 When FFmpeg is enabled:
@@ -427,7 +429,7 @@ The diagnostic endpoint exposes deployment details and should be restricted or r
 <script>
   window.CYBERCHAT_BASE = '/chat';
 </script>
-<script src="/chat/assets/js/cyberchat-app.js?v=20260609.7"></script>
+<script src="/chat/assets/js/cyberchat-app.js?v=20260609.8"></script>
 <script>
   CyberChat.init('#my-chat');
 </script>