[Lucalopezz]

Login and registration currently wait for a separate API health round, while a global controller polls health and coordinates connection notices and recovery. Remove that browser supervision so validated forms submit directly and failed page loaders retry their own request.

Keep GET /api/health for monitoring and deployment readiness checks. Preserve GET/HEAD deadlines, one retry for temporary read failures, single-send mutations, form drafts, and the distinction between HTTP 401 and temporary outages. Restore TanStack Query's normal stale-query refetch on visibility/reconnection so the shared session profile is checked directly when returning to the app.

Vercel's container runtime can still scale down when idle. This removes extra browser requests and request gating; it does not claim to eliminate cold starts. The updated API connection guide explains responsibilities and trade-offs.

Closes #19

Validation

• TDD: six regression cases failed against the previous implementation: public-route health probes, gated login/registration, and health-gated private-loader retry.
• All 432 web tests pass across 64 files using NODE_OPTIONS=--no-experimental-webstorage pnpm --filter web test --maxWorkers=2.
• All 8 focused Chromium tests pass across API availability and route access, covering lost login responses, deliberate retry, idle/browser events without health polling, protected reloads, and 401 handling on return.
• Web lint, production build, browser-test TypeScript checks, and git diff --check pass. The build retains the existing large-chunk warning.
• The initial unrestricted Vitest run hit memory pressure and timeouts; the complete run passes with two workers. Browser API responses are intercepted, so they establish frontend behavior rather than production latency or backend cookie correctness.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
devlog-unified-preview	Ready	Preview	Oct 24, 2026 12:09pm UTC