[vincentfranstyo]

With Wi-Fi off, pressing Generate spun forever and the backend never received POST /generate; the request went out the moment the network came back. TanStack Query pauses every new request while the browser reports offline, but Voicebox's backend is a local sidecar that never needed the network. Local API calls now run regardless of that flag.

Fixes #1085

Before (upstream/main)	After

Red box: the Generate button after one click while the page reports offline. Before: stuck spinner and no POST /generate. After: the request was sent and the form reset.

Try it: 1. Start the app with a cached model. 2. Turn Wi-Fi off (or run window.dispatchEvent(new Event('offline')) in the devtools console). 3. Click Generate. The generation starts instead of spinning.

Note: The Tauri and web entry points each built their own QueryClient with a copy of the app's defaults, so a fix to the shared client alone would not have reached the desktop app. Both now import the shared one. Side effect: the server-URL change handler already invalidated the shared client; in the desktop and web builds that was a different instance from the one rendering, so it was a no-op there. It now works.

Trade-off for remote-server mode (a non-loopback server URL, or the Docker web UI): with networkMode: 'always' a request made while the browser reports offline is sent at once and fails with a fetch error (then one retry) instead of pausing and resuming when the network returns, and TanStack's refetchOnReconnect is off, so a query that failed offline waits for its stale time or interval rather than refetching on reconnect. Fail-fast with a visible error seemed better than a silent spinner in both modes; scoping the mode per server URL is possible if you would rather keep the pause for remote servers.

Tests and plan check

• Unit: n/a, the repo has no frontend test runner. Standalone check against the installed @tanstack/react-query 5.90.20:

  default client      : status=pending isPaused=true requestSent=false
  networkMode 'always': status=success isPaused=false requestSent=true
  

• Integration: n/a, no backend change.
• End-to-end: Playwright drove the web build against a stub backend, dispatched the offline event, clicked Generate:

  before-fix: POST /generate sent=0 spinner=true
  after-fix:  POST /generate sent=1 spinner=false
  

  Chromium's own offline emulation was not used because it also blocks loopback; the offline event alone is what flips TanStack's online manager, matching the reporter's situation.
• tsc for app and web: clean. vite build for the Tauri frontend: clean. Biome clean on the three touched files (the two entry points had pre-existing import-order errors that the second commit fixes, since this PR rewrote those blocks).
• Each acceptance criterion from the plan is met; proof: AC1 diff, AC2 screenshots and logs above, AC3 command runs above, AC4 grep 'new QueryClient' finds one site.
• Plan was challenged by an independent reviewer before building, and the open PR was reviewed again by a second one; the E2E method, the remote-mode trade-off note and the import fix came from those reviews.
• Not verified here: that macOS WKWebView fires offline on Wi-Fi off (the reporter's symptom implies it does). Linux host, no Tauri desktop run.

🤖 Generated with Claude Code using the ship-pr workflow