Long-open tabs keep running the JS bundle they first loaded, so a shipped
change can look "missing" (e.g. a new settings field appearing only after a
full reload) until the whole app is reloaded. Add a small, unobtrusive prompt
that detects a newer deploy and offers a one-click reload.
- next.config: inline the deploy's commit SHA into the client bundle as
NEXT_PUBLIC_BUILD_ID (empty in dev / self-hosted, which disables the check).
- /api/version: public, no-store route returning the running deployment's SHA
at request time.
- DeployReloadPrompt: compares the two on load, on tab focus, and on a 30-min
backstop; shows a bottom banner with "Ladda om" on mismatch. Mounted once in
the root layout. No service worker, degrades to a no-op with no build id.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>