Reconsider the land-on-Overview redirect when the analytics probe fails

[kylebernhardy]

Follow-up from the PR #1476 — keep Overview usable when the analytics capability probe fails approval review (non-blocking suggestion that merged with the PR).

Current behavior: when the get_analytics capability probe fails while the user is on a chart tab, StatusTabs does a one-shot replace navigation to the Overview tab — landing them on live data (get_status-backed) instead of a dead panel. Chart tabs remain reachable and show the Retry notice.

The reviewer's question: silently replacing the user's explicitly-opened chart tab may be more surprising than staying put and showing the Retry/unavailable notice in place. It's a deliberate, documented UX judgment call ("open on live data"), but worth a product decision:

• Keep (current): failure lands you somewhere useful; the notice explains chart tabs.
• Stay put: no navigation on failure; the opened tab shows the analytics-unavailable notice with Retry, and Overview is one click away.

Whichever way, the one-shot/bounce-back guard logic in StatusTabs.tsx stays (it's what makes either behavior stable). Regression tests for the redirect live in __tests__/StatusTabs.capability-gating.test.tsx and would flip with the decision.

Filed from merged-PR review follow-ups.

Comment generated by kAIle (Claude Fable 5)