[akirilyuk]

Summary

A same-session reconnect attempt that starts while the network is still coming back can have every ICE candidate pair fail within a second or two. The ICE agent does not retry failed pairs, so that peer connection can never connect, but the client kept waiting on it through the settle time, the settle extension and the in-flight grace, and never made a second attempt.

• While a reconnect attempt settles, the client checks its candidate pairs once per second. When every pair has failed on two checks in a row, it logs session/reconnect_attempt_ice_failed and starts the next attempt right away.
• A dead attempt no longer counts as "in flight", so it does not get the grace at the end of the budget. If it dies during the grace, recovery ends at once.
• Release 0.11.7 (version + CHANGELOG).

Tests

browser-voice-session-recovery.test.ts: the mock peer connection now returns candidate-pair stats. New cases: all pairs failed → next attempt without waiting for settle; one failed check is not enough; pairs in progress keep the attempt; dead during the grace ends recovery; dead attempt in backoff at budget end gets no grace; attempt 2 after a dead attempt restores the session.

Verified locally and in CI; no extra manual steps.

🤖 Generated with Claude Code