Fix workspace switch cache isolation

[baxen]

Summary

• scope React Query caches to the active workspace by creating a fresh query client per workspace boundary
• gate workspace-scoped UI on the exact workspace config applied to the Tauri backend
• keep the app updater provider outside the workspace reset boundary

Testing

• cd desktop && pnpm exec biome check src/app/App.tsx src/main.tsx src/features/workspaces/useWorkspaceInit.ts src/shared/api/queryClient.ts
• cd desktop && pnpm exec tsc --noEmit
• manually tested switching between two workspaces and confirmed stale channel lists no longer persist

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4c4cf2a541

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Exclude reinit-only key from workspace reset trigger

Adding workspaceKey to this effect’s dependencies makes every reconnectWorkspace() bump run resetWorkspaceState(), even when the active workspace is unchanged. In the deep-link flow, reconnectWorkspace() is always called after connect handling, so reconnecting to an already-active relay now clears module caches such as drafts (clearAllDrafts) and search hits for the same workspace, which is user-visible data loss rather than cross-workspace isolation.

Useful? React with 👍 / 👎.