fix-status-badge-reactive
🐛 Bug Fixes
Status badge stuck on "Need reload" after config reload
Goal: After reloading the configuration from the Status page, the init report turned green and the notification banner disappeared, but the status badge stayed on "Need configuration reload" until the user clicked elsewhere (UI-only desync).
Solution: The Status page read its state solely from useLoaderData() (a snapshot frozen when the route loader ran), while AppLayout reads the live ['status'] query. Invalidating ['status'] in the reload onDone updated the cache and the banner, but not the loader snapshot. This desync was previously masked by the router being recreated on every status change (which re-ran all loaders); removing that churn (router singleton fix) exposed it. Fix: the Status page now derives its status from a live useQuery(['status']), seeded with the loader value via initialData to avoid any flash — consistent with AppLayout.
Files Modified:
ui/src/pages/settings/Status.tsx- read status from liveuseQuery(['status'])instead of the loader snapshot only