feat(mobile): switch between signed-in T3 accounts

[rachelagent]

Mobile users with more than one T3 Connect account have to sign out and sign back in to move between them. Once Clerk multi-session is enabled on the instance, Clerk's native profile view (already used for Settings → T3 Account) shows Add account and Switch account on both iOS and Android. We don't need a custom switcher.

Before this PR, a switch from account A directly to B was a corner case. CloudAuthBridge handled it inside one untested effect. With multi-session it becomes the main path, so the logic now lives in cloudAccountSync.ts, a small controller with tests. CloudAuthBridge feeds it the current Clerk session and the set of signed-in accounts.

The controller tracks the installed account: whose drafts and relay environments are on the device. When the user switches from A to B, it:

1. Deactivates the relay session right away, so neither account's relay state can be read during the switch.
2. Saves A's environment list (while A stays signed in), then archives A's drafts, disconnects A's relay environments, clears the relay token cache and unregisters A's push device.
3. Installs B: restores its drafts and, if B has a saved list, reconnects those environments with no onboarding. T3 Connect onboarding only appears for an account this device has nothing saved for.

Signing out forgets that account's saved environments, including an account that isn't active. Signing out of one account while another stays signed in falls through to the remaining account, which reconnects its saved environments.

Each account's relay token reader is bound to its own Clerk session. That way the cleanup that runs after a switch unregisters the previous account's push device, not the new one's.

Races and crashes fail safe:

• A cold start never onboards.
• If switches come in faster than cleanup, only the last account activates, and skipped accounts keep their saved lists.
• A failed cleanup keeps the next account inactive, and the next attempt retries it.
• The list is saved before removal, and deleted only once restored. So an interrupted cleanup keeps the complete list, and an interrupted restore resumes on the next start.
• A switch made while the app was closed is handled on the next start.

One account is active at a time. Keeping every account connected at once is a later PR.

Stacked on pingdotgg#2829's branch (t3code/codex-turn-mapping). Multi-session is not yet enabled on the production Clerk instance. Until it is, the native view hides the new rows and behavior is unchanged.

Testing

• vp test run src/features/cloud in apps/mobile: 47 passed. The cloudAccountSync tests cover:
  • cold start
  • switch ordering
  • reconnecting saved environments when switching back, with no onboarding
  • accounts with no environments
  • repeated Clerk sessions, both before and during install
  • rapid switches, including skipped accounts keeping their lists
  • a failed cleanup retried against the right account
  • interrupted cleanups and restores
  • a switch made while the app was closed
  • sign-out, including an inactive account and signing straight back in
  • cancellation
• tsc --noEmit for mobile, plus vp lint on the changed files: clean.
• Three rounds of review by a separate model. Each finding was checked against the code, and each fix has a regression test that fails without it.
• The screenshots and recording come from one scripted, unattended run, repeated against the final commit with the same result.

Recording

One scripted take:

1. Sign in as alpha and connect Alpha Studio from onboarding.
2. Add bravo and connect Bravo Workstation.
3. Switch back to alpha. Alpha Studio reconnects without onboarding.
4. Sign out of alpha. The app falls through to bravo, and Bravo Workstation reconnects.

Idle stretches are trimmed.

account-switching.mp4

Screenshots

Captured on an iOS 27 simulator running this branch. A local mitmproxy addon stands in for Clerk multi-session and the T3 Connect relay. Each account has its own relay environments, backed by real local T3 servers. "Alpha MacBook" is listed but has no server behind it.

1. Sign in as alpha: a new account, so onboarding lists its environments

Signed out	Clerk sign-in	Onboarding	Alpha Studio connected

2. Add bravo: alpha's environments are disconnected and saved, bravo onboards

Home as alpha	Bravo onboarding	Bravo Workstation connected	Home as bravo

3. Switch back to alpha: Alpha Studio reconnects, no onboarding

Switch account	Alpha's environments	Home as alpha

4. Sign out of alpha: the app falls through to bravo, whose environment reconnects

Bravo's environments

Opus 5.5 via Claude Code in T3 Code.

🤖 Generated with Claude Code

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for bd04637.

This comment will update automatically after the next completed run.