Desktop isolated mode

Turn on Run my own separate server in Settings (off by default). With it on, the desktop app stops probing for an existing server. It spawns its bundled server on its own port, chosen by a free-port scan starting at 4100 (clear of the 4000 range a dev server uses), and points it at a data profile of its own.

The isolated data profile lives in your base data directory with a -desktop suffix (set via REPO_DASHBOARD_DATA_DIR), so it never shares state with a from-source run.

The first time you flip isolated mode on, RepoOps seeds the fresh profile from your standard one so you are not starting from a blank slate. It imports a safe subset:

• Your accounts, tracked repos, and settings.
• A copy of the data-dir .env (per-repo export tokens).

Telemetry and caches start fresh and accumulate on their own. If the import cannot complete, the app falls back to a clean first-run profile rather than a half-copied one. The change takes effect on the next restart, never as a hot swap.

Open Settings, App, the Desktop server section (next to Launch RepoOps at login). It shows the current backend mode and port, the toggle, and a Restart RepoOps to apply prompt. Restart and the app comes back on its own isolated server.

• Windows autostart. The login Scheduled Tasks for the dashboard and the capture daemon now launch through the hidden launcher, so there is no console window flashing at logon.
• Source-mode auto-update. Server runtime writes no longer dirty the disposable runtime worktree, so a running app stops wedging its own update behind a dirty-tree check.
• Update banner. Update prompts are audience-aware: the desktop shows a quiet auto-updating state, a browser sees a new-version notice.