fix(web): track switch dialog no longer offers a switch that moves nothing#27484

Problem

In Settings → About → Update track, the "Switch to Stable?" dialog can skip every remote (for example one whose server predates database checks) while this app has nothing to reinstall. The Switch to Stable button still looks like it will switch something. Clicking it moves no machine and shows no message. From the Review link it does nothing at all.

Reproduced on main at 305a90dce4. The client was the desktop app (0.1.5, Stable) under Xvfb; the remote was the published t3@0.1.4-nightly.20261028.3824 server, reporting serverSelfUpdate: boot-service and no databaseMigration, the same build as the report.

• Following the report's steps (saved track Nightly, pick Stable, confirm): the dialog listed only "1 skipped — its server predates database checks; update it on Nightly first". Confirming sent no request to the remote (its trace had no update spans), showed no toast, and only changed the local saved track.
• Through the Review link (saved track already Stable): the same click did nothing.
• An unmanaged remote skipped as "needs a manual update", while switching to Nightly, behaves the same way.

Change

The dialog now treats "no machine moves" (this app does not reinstall and every listed row is skipped) as its own case, decided by a small pure helper, nothingToMove:

• If confirming would still save a track (the saved track differs, or a desktop host that already runs the target track still gets a track-only request), the button stays enabled and the dialog says so: "No machine can switch to Stable now. This only saves the track." The old "Every connected machine is already on Stable. This only saves the track." note is the same case with no rows.
• If confirming would neither move a machine nor save a track, the button is disabled with "No machine can switch to Stable now."

"This app cannot switch: …" still takes priority. Target selection, skip reasons, database checks and the run itself are unchanged.

Scope and approval

Fixes pingdotgg/t3code#27461

Triaged via the automated issue flow; GitCafe issue #27461.

Verification

• vp test run apps/web/src/components/settings/updateTrackSwitch.logic.test.ts: 6 passed (one more case covers an unknown saved track). The new nothingToMove cases cover:

  • the issue case: every remote skipped and the track already saved, so the button is disabled;
  • the select path: the note is shown and the button stays enabled;
  • a track-only desktop host: the button stays enabled;
  • this app's updater off while it runs the other track;
  • plans where a machine moves: no change.

  Removing the hasTargets check fails the track-only case.

• vp run check:changed: format, lint, knip, typecheck, tests and React compiler all pass.

• Real app, before (305a90dce4) and after (69db3511; later commits only bring in main and make the dialog stay enabled while the saved track is still unknown, which these states never hit). Desktop app on Linux (Electron 44.10.0, DPR 1, 1280×800 dark/light, plus the smallest desktop window 840×620), with the same scripted interaction on fresh state for both sides:

  Row	Before	After
  F01: only remote skipped (server predates database checks), pick Stable while Nightly is saved	No note; Switch to Stable enabled	"No machine can switch to Stable now. This only saves the track."; enabled; confirming saves Stable
  F02: same remote, Review with Stable already saved (1280×800 dark; 840×620 light with two skipped machines)	Enabled; clicking or Enter closes the dialog and does nothing	Disabled with "No machine can switch to Stable now."; clicking or Enter does nothing and the dialog stays open
  F03: no other machines, pick Stable while Nightly is saved	"Every connected machine is already on Stable. This only saves the track."	Identical (zero changed pixels)
  F04: same, Stable already saved	Same note; enabled	Disabled with "Every connected machine is already on Stable."
  F05: this app's updater off, pick Nightly, no other machines	Only "This app's updates are off here…"	Adds "No machine can switch to Nightly now. This only saves the track."; enabled
  F06: same, Nightly already saved	Enabled	Disabled with "No machine can switch to Nightly now."; updater-off note stays
  F07: a desktop host already on Stable gets a track-only request (after only)		Enabled; confirming sends the track request
  F08: one moving server plus one skipped remote (after only)		No new note; enabled

  Besides the footer and notes, the only other differences are layout effects: the dialog grows or shrinks and re-centres when a note appears or disappears. The before/after screenshots and recordings will be attached to this section.

• Not checked: a real update completing on a track-only desktop host (F07 stops at the request: the dev build has no update feed), and the optional rows where this app itself reinstalls.

Model and harness: Claude Opus 5.5 (Claude Code in T3 Code) as lead and implementer, with GPT-6.1 Sol (Codex) and Claude Opus 5.5 reviewers.

🤖 Generated with Claude Code