fix(dashboard): reuse cached API reads

[dcramer]

Dashboard routes now reuse a shared TanStack Query cache instead of treating each mount as a fresh read. Shell identity and configuration have one owner, slower-changing metadata stays fresh for five minutes, reporting reads use the shared 30-second default, and request-backed queries consume Query's cancellation signal. Fresh conversation feeds no longer refetch merely because the window regains focus.

Personal API token reads and writes now use the query and mutation caches without storing the one-time token secret. Cache updates cancel stale reads before applying results, rapid create clicks cannot start duplicate mutations, and plugin record actions are serialized so rapid clicks cannot issue duplicate deletes. Query keys now include every input used by conversation, plugin-page, and highlighted-code fetches, while conversation detail consumers subscribe only to the fields they use.

The dashboard now runs TanStack Query's recommended lint rules through Oxlint in both the root lint task and pre-commit checks. ESLint is present only because the TanStack plugin requires its runtime as a peer; Oxlint remains the configured runner. Browser regression coverage exercises single /api/me ownership, route-level token cache reuse and mutation races, fresh versus stale focus behavior, and duplicate plugin actions.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
junior-docs	Ready	Preview	Aug 1, 2026 7:53pm

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 07120ce. Configure here.}