fix(web): every reconnect gets its own grace period before the unavailable banner

[juliusmarminge]

After an environment's reconnect outlasted the grace period, its next reconnect showed the "unavailable" banner straight away, even for a short blip.

#20418 removed the effect that reset the grace, so the elapsed grace stayed recorded for that environment after it reconnected. The reset now happens during render whenever the reconnecting environment changes, including when it goes back to none, so each attempt gets its own grace period.

Found by Macroscope's review of #20418.

🤖 Generated with Claude Code (Claude Opus 5.5)

---

[macroscopeapp]

Approvability

Verdict: Approved at 9b00d4c

Macroscope's review found this PR approvable — This single-file, nine-line fix only resets reconnect grace-period state when the active reconnecting environment changes, preventing stale state from suppressing later grace periods. It is a localized UI behavior fix with no schema, configuration, infrastructure, or security impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Team
• Run ID: c3ec19bd-0f72-44e8-ac55-55926cbae9ff

📥 Commits

Reviewing files that changed from the base of the PR and between f5cb328 and 9b00d4c.

📒 Files selected for processing: 1

• apps/web/src/components/ChatView.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.

📝 Walkthrough

Reconnect warning grace tracking now resets when the active reconnecting environment ID changes. A later reconnect attempt to the same environment starts with the elapsed-warning state cleared.

Changes: Reconnect grace tracking

Layer / File(s)	Summary
Reset grace state on environment change apps/web/src/components/ChatView.tsx	When the active reconnecting environment ID changes, the code updates the tracked ID and clears the elapsed-warning state.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

Suggested reviewers: maria-rcks

Merge Risk: ⚪ Minimal · up to 9b00d

Each new reconnect lifecycle receives a fresh grace period, and the reviewed change presents no identified merge-blocking risk.

Pre-merge checks: 3 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description explains the problem and the code change, but it does not provide the required Problem, Change, Scope and approval, or Verification sections. It also omits focused verification results…	Organize the description under the required headings. Add scope or maintainer approval details, explain why a prior issue was not required if applicable, and document focused tests or manual checks with observed results. Include before/afte…

Passed checks: 3 passed

Check name	Status	Explanation
Title check		The title clearly and concisely describes the reconnect grace-period fix and the unavailable banner behavior.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description explains the problem and the code change, but it does not provide the required Problem, Change, Scope and approval, or Verification sections. It also omits focused verification results and UI evidence for the timing-related behavior.

Resolution

Organize the description under the required headings. Add scope or maintainer approval details, explain why a prior issue was not required if applicable, and document focused tests or manual checks with observed results. Include before/after screenshots and a short recording if needed to demonstrate the reconnect timing behavior.

• Fix all pre-merge checks with AI

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}