fix: redirect to home on 401 instead of showing error boundary

When server credentials change, stale browser sessions get 401 on API calls.
Intercept all 401 responses globally and navigate to "/" so the user can
re-authenticate, rather than showing an unrecoverable "Something went wrong".
Using a never-resolving Promise prevents the SDK error from propagating to
the error boundary before navigation completes.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: 2 people

packages/app/src/entry.tsx

@@ -153,6 +153,20 @@ if (import.meta.env.VITE_SENTRY_DSN) {
   })
 }
 
+// Intercept 401 responses: if credentials are stale and we're not on the home
+// page already, navigate to "/" so the user can re-authenticate.
+const _nativeFetch = globalThis.fetch.bind(globalThis)
+const _interceptedFetch = async (input: Parameters<typeof fetch>[0], init?: Parameters<typeof fetch>[1]): Promise<Response> => {
+  const response = await _nativeFetch(input, init)
+  if (response.status === 401 && window.location.pathname !== "/") {
+    window.location.href = "/"
+    return new Promise<Response>(() => {})
+  }
+  return response
+}
+Object.assign(_interceptedFetch, globalThis.fetch)
+globalThis.fetch = _interceptedFetch as unknown as typeof fetch
+
 if (root instanceof HTMLElement) {
   const auth = authFromToken(new URLSearchParams(location.search).get("auth_token"))
   clearAuthToken()