Updater status is only visible on the Settings Updates tab #697

Surfaced by review of #696 (the Settings tabs restructure).

UpdateControls renders the updater's role="alert" / role="status" element, and it now mounts only with the Updates panel. UpdateBanner deliberately renders nothing for failed, cancelled, checking, current or applying — there is an explicit test asserting failed stays out of the global banner.

So a backend-driven transition to failed while the user sits on another Settings tab produces no visible or announced feedback until they select Updates. Before the restructure every section was on one scroll, so it was visible whenever Settings was open.

Note this does not apply to a manual check that throws: runUpdate in src/App.tsx catches and calls setError, and the app-level error banner renders outside the view regardless of tab. The gap is backend-pushed failed states.

Options

1. Render all five panels and mark inactive ones hidden. Keeps the element mounted and would also let aria-controls be set on every tab rather than only the selected one. Note role="alert" still does not announce while hidden, so this fixes visibility-on-return, not announcement.
2. Surface backend-pushed failed through the global banner — but an existing test asserts the opposite, so this is a deliberate product decision to revisit rather than a bug to fix.
3. Accept it as inherent to tabbed navigation and mark the Updates tab when it needs attention.

Worth a product call before implementing.