Files
pipelines/app/notes/multiple-servers.md
T

4.0 KiB

Multiple servers and double-back home exit

User selected automatic fallback: named logical servers each have ordered preferred/backup addresses. Switching logical servers is explicit, never an automatic response to a network failure. User also requested two Android Back presses at home to exit; details/dialogs still use one normal pop.

Item Source Verification Landing Deployment
Immutable saved profiles/migration 289a971b + afb97c75 Roundtrip, ordered aliases, validation, failed writes, catalog-reset binding Merged main Pending
Ordered socket fallback b2e5606c 22 transport tests; bounded connect, cancellation, stale callbacks, no mutation replay Merged main Pending
Per-profile sign-in and trusted origins ae72e0fc + integration clearSelection 30 focused tests; aliases share only explicitly trusted cookies; sign-out and async login races isolated Merged main Pending
Native/root/settings integration Manager integration Root switch/dispose/reset and cache-isolation tests; full acceptance pending Pending commit Pending
Stable launch recovery across aliases afb97c75 + manager wiring Original request key survives legacy storage migration and preferred address changes Merged + integration pending Pending
Double-back home exit 4e6771aa + Search-tab integration First Android root Back hints; second within 2s falls to platform; navigation/dialogs/expiry clear window; iOS/web unaffected Merged + integration pending Pending

Behavior and preservation

  • Settings → Servers: add/edit/remove named configurations, one address per line in preferred order; explicitly select a different server.
  • Root disposes the previous app/socket before activating the new credential namespace, resets routes and remounts feature state. Alias fallback retains the same logical server identity and never replays outstanding/queued mutations.
  • Cookie, chat draft/instructions/read marks, workspace and notification/dismissal storage are isolated per server. Existing original local data stays with the migrated original server; legacy keys are retained for rollback.
  • Legacy credential identity is bound before connection and cannot be rebound to another server merely by deleting the catalog. The original endpoint pointer is preserved solely to recover old pending-launch keys, never as a network alias.
  • Browser sockets stay on their page origin. Selecting another browser server opens its page; browser Back/reload reconciles selection to the actual origin. Native builds provide automatic primary/backup address fallback.
  • Explicit ws:// LAN profiles are allowed by Android, with cleartext/trusted-link warnings. No TLS downgrade, server discovery or cross-profile cookie forwarding.

Evidence so far

  • 61 focused integration/profile/onboarding/migration tests pass; an additional native-root fallback regression is included for final acceptance.
  • Browser normal-app profile flow passes 8 checks/5 captures on each host: build/server-profiles-material/, build/server-profiles-cupertino/. Covers existing-address migration, alias editing, add without auto-switch, reload, cross-origin page navigation, Back restoring actual selection, removal.
  • Browser discovery: a temporary loading MaterialApp reset deep-link URLs before the real Router mounted. Loading no longer owns an App/Navigator.
  • Full suite caught two regressions and they were corrected: the isolated gate test explicitly disposes its now-time-bounded connection before teardown; the explicit openSearch API still restores its return route, while the Search tab participates in home double-back. All 32 focused application regressions pass.
  • Read-only security review identified three concrete issues (legacy identity rebinding, browser selection mismatch, migrated pending-launch key changes); fixes were re-reviewed with no remaining findings in that scope.
  • No backend edits, production chat/run mutations, device use or phone installation. Actual Android device behavior remains unverified.