fix(app): back off event stream reconnects after repeated failures - #48015

Been poking at reconnect behavior lately (see #48161 on v2 — client-side backoff, different layer, so no overlap here), so I read through this diff.

Main thing: the consecutiveErrors = 0 at the top of the for-await means a server that accepts the stream, emits a single event and then dies gets the full 250ms base delay again on every cycle, forever. That flapping pattern is basically where backoff earns its keep, so maybe reset the counter only after the stream has stayed healthy for a bit (say N seconds of events) instead of on first event.

Nit: with the 5s cap, the exponent clamp Math.min(consecutiveErrors, 8) can't actually engage at this base — 250ms x 1.5^7 is ~4.3s and anything beyond that hits the cap anyway, so the clamp is dead code unless the base ever drops under ~200ms.

#48014 looks assigned internally, so if this overlaps with planned work no worries — leaving notes in case they're useful.

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.