fix(stt): Soniox dies for the rest of a meeting after a hidden/idle stretch — self-heal on resumed audio

[averatec0773]

Summary

Soniox STT silently dies for the rest of a meeting after the app is hidden/idle for a while — come back, speak, and transcription is gone with the UI stuck on "STT reconnecting". Only ending + restarting the meeting recovers it.

Root cause: after RECONNECT_MAX_ATTEMPTS (10) failed reconnects, scheduleReconnect() latches shouldReconnect = false permanently. During a silent/hidden stretch the exponential-backoff ladder burns all 10 attempts (~2 min), so when audio flows again write()'s lazy-reconnect sees the latch and never reconnects.

Fix: genuine audio at write() means the pipeline is alive and the user wants transcription again — grant the session one fresh reconnect budget instead of staying dead. A 15 s cooldown rate-limits revival so a genuinely-dead endpoint can't be re-stormed every chunk; a user stop() is never revived. The attempt cap, backoff ladder, and F-203 stale-socket guards are unchanged.

Fixes #

Type of Change

• 🐛 Bug Fix

Testing & Environment

• New pure decision helper electron/audio/sttReconnectPolicy.mjs (same pattern as the repo's other .mjs logic helpers).
• SttReconnectRevival.test.mjs — 8 pure-function tests: the reported hidden→exhausted→resume scenario, cooldown boundary (>= inclusive, -1 waits), user-stop never revives, stop-latch-with-null stays dead, in-flight/live-socket guards, second-exhaustion re-arms its own cooldown.
• SonioxReviveWiring.test.mjs — 4 integration tests driving the real compiled SonioxStreamingSTT.write() (connect() stubbed, no socket/network): revives after cooldown, does not before it, never revives a stopped session.
• 12/12 pass; strict (TS7) typecheck and build:electron clean.
• Automated only — no manual audio session was run; the tests reproduce the exact state transitions.

Scope

• Fixes Soniox (the provider that exhibited the bug). Deepgram / ElevenLabs / nvidia share the same RECONNECT_MAX_ATTEMPTS latch pattern; the pure sttReconnectPolicy.mjs helper is reusable and applying it to them is a clean follow-up, kept out of this PR to keep the change focused.

[greptile-apps]

Greptile Summary

The PR allows an active Soniox transcription session to recover after exhausting its reconnect budget when audio resumes after a cooldown.

• Records when automatic reconnect attempts become exhausted.
• Grants a fresh reconnect budget when later audio proves the session remains active.
• Adds pure policy tests and compiled-class wiring coverage.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
electron/audio/SonioxStreamingSTT.ts	Adds exhaustion tracking and safely revives active sessions after resumed audio, while preserving the user-stop latch.
electron/audio/sttReconnectPolicy.mjs	Defines the pure cooldown and lifecycle guards governing reconnect revival.
electron/audio/tests/SonioxReviveWiring.test.mjs	The previous silent-skip issue is fixed by importing the compiled class at module load so a missing build fails explicitly.
electron/audio/tests/SttReconnectRevival.test.mjs	Covers cooldown boundaries, stopped sessions, connection guards, and repeated exhaustion cycles.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Soniox reconnect budget exhausted] --> B[Latch reconnect off and record timestamp]
    B --> C{Audio arrives after cooldown?}
    C -->|No| D[Remain latched off]
    C -->|Yes, session active| E[Reset reconnect attempts]
    E --> F[Reconnect Soniox WebSocket]
    C -->|Session stopped| G[Do not reconnect]

Loading

_{Reviews (2): Last reviewed commit: "fix(stt): Soniox STT dies for the rest o..." | Re-trigger Greptile}