fix(web): make onboarding a shared multi-computer wizard

[juliusmarminge]

Onboarding required extra screens and repeated setup for each computer, used a separate visual style, and could remain visible after completion. This makes setup an app overlay using the shared wizard components: inline pairing and Connect discovery, computers selected by default, grouped agents and project import, compact selectable project rows, and stable loading/expansion transitions.

Connect selection stays in its own section, preserves explicit deselection, and shows full connection errors in tooltips. Completing setup dismisses the overlay before draft navigation. Onboarding follows the app theme.

Validation: web typecheck; 83 focused tests covering discovery/selection, project identity and import helpers, first-run decisions, provider wizard navigation, and theme handling; browser verification against a disposable local server, plus maintainer verification of signed-in Connect on the preview. Web and desktop share this UI; mobile and wire contracts are unchanged. Local Clerk sign-in is unavailable with the production key, so the local captures show its loading state.

Before/after below use the actual base and head with the same server, data, dark appearance, and 1280×1000 viewport.

Before	After

Project selection:

Inline expansion, step navigation, and dismissal:

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e83245b34f86b135/t3-pr-flow.mp4

Prepared with GPT-6 in Codex.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR substantially changes the first-run product flow into a shared multi-computer wizard, including automatic computer selection, environment connections, multi-machine agent checks, project scans/imports, routing, and theming. Because it changes onboarding behavior and product defaults across several runtime components, the scope warrants human review.

Not approved because:

• Monthly spending limit reached (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings. You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.5 KiB	−15 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+3 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−18 B (−0.3%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	8	8	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−36 B (−0.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.1 KiB	7.1 KiB	+3 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.5 KiB	−39 B (−0.6%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.8 KiB	−88 B (−0.1%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: f5fb056 · PR result: ba85477 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 113.9 KiB
• Claude decoded thread snapshot: 114.6 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.