Seen on the release build: after the local backend restarted, the first
retry reached it but the session was confirmed 13 s later, past the 5 s
wait, so the session fell into an incident and never came back. An
offline retry that times out on a connected server now stays offline and
asks again in 2 s, up to three times, before it is treated as today.
The setup warning is no longer hidden for such a retry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>