@oxyhq/services 13.3.0 → 14.0.0

package/lib/commonjs/ui/context/OxyContext.js

@@ -9,7 +9,6 @@ var _core = require("@oxyhq/core");
 var _bloom = require("@oxyhq/bloom");
 var _authStore = require("../stores/authStore.js");
 var _shallow = require("zustand/react/shallow");
-var _useSessionSocket = require("../hooks/useSessionSocket.js");
 var _useLanguageManagement = require("../hooks/useLanguageManagement.js");
 var _useSessionManagement = require("../hooks/useSessionManagement.js");
 var _useAuthOperations = require("./hooks/useAuthOperations.js");
@@ -23,10 +22,10 @@ var _queryClient = require("../hooks/queryClient.js");
 var _useAvatarPicker = require("../hooks/useAvatarPicker.js");
 var _accountStore = require("../stores/accountStore.js");
 var _useWebSSO = require("../hooks/useWebSSO.js");
-var _silentGuardKey = require("../../utils/silentGuardKey.js");
 var _crossApex = require("../../utils/crossApex.js");
 var _inSessionTokenRefresh = require("./inSessionTokenRefresh.js");
 var _silentSessionRestore = require("./silentSessionRestore.js");
+var _index = require("../session/index.js");
 var _jsxRuntime = require("react/jsx-runtime");
 const OxyContext = /*#__PURE__*/(0, _react.createContext)(null);
 
@@ -34,8 +33,8 @@ const OxyContext = /*#__PURE__*/(0, _react.createContext)(null);
  * Result of {@link OxyContextState.signInWithPassword}.
  *
  * `'ok'` — the password was accepted and the resulting session has been
- * committed into context state (the SAME path FedCM / SSO sessions use), so
- * `isAuthenticated` / `user` are updated and the session is durably persisted;
+ * committed into context state (the SAME path SSO / silent-restore sessions
+ * use), so `isAuthenticated` / `user` are updated and the session is durably persisted;
  * the caller can proceed (e.g. navigate into the app).
  *
  * `'2fa_required'` — the account has two-factor auth enabled, so NO session was
@@ -47,41 +46,6 @@ const OxyContext = /*#__PURE__*/(0, _react.createContext)(null);
 // `../utils/activeAuthuser` so the session-management and auth-operations hooks
 // can share them without re-importing this 1k-line context file.
 
-/**
- * Module-level run-once guard for the cold-boot `fedcm-silent` step.
- *
- * The FedCM silent step triggers a one-shot `navigator.credentials.get`
- * handshake that must fire AT MOST ONCE per page load — otherwise a provider
- * remount storm (route churn, StrictMode double-invoke, error-boundary
- * recovery) becomes a credential request storm. A per-instance ref resets on
- * every remount, so the guard must live at module scope. Keyed on
- * `origin|baseURL` so two providers pointed at the same API from the same
- * origin share one attempt; never cleared because only a fresh page load can
- * change the central IdP session state, and a fresh page load starts a fresh
- * module scope.
- *
- * This is a dedicated set — distinct from `useWebSSO`'s `silentSSOAttempted`
- * (which guards the post-boot INTERACTIVE button path) and never a core
- * module-level singleton (that re-evaluates under Metro web bundling and the
- * guard would not hold).
- */
-const servicesSilentAttempted = new Set();
-
-/**
- * Build the `origin|baseURL` signature used as the silent-cold-boot guard key.
- */
-function silentColdBootKey(oxyServices) {
-  // `buildSilentGuardKey` reads `window.location.origin` behind a guard that
-  // also verifies `window.location` exists. This is critical: it runs
-  // UNCONDITIONALLY at the top of `restoreSessionsFromStorage` (before the
-  // cold-boot try/catch) on EVERY platform, and React Native aliases a global
-  // `window` with NO `window.location`. Without that guard the read threw
-  // `Cannot read property 'origin' of undefined` on native, escaping the
-  // restore path so `markAuthResolved` never ran and stored-session restore was
-  // never reached.
-  return (0, _silentGuardKey.buildSilentGuardKey)(() => oxyServices.getBaseURL?.());
-}
-
 /**
  * Per-step fail-fast budget for the cold-boot silent iframe (`silentSignIn`
  * against the per-apex `/auth/silent` host).
@@ -96,18 +60,6 @@ function silentColdBootKey(oxyServices) {
  */
 const SILENT_IFRAME_TIMEOUT = 2500;
 
-/**
- * Per-step fail-fast budget for the cold-boot refresh-cookie restore
- * (`refreshAllSessions`).
- *
- * On a cross-domain RP the `Domain=oxy.so` refresh cookie never reaches
- * `api.<apex>`, so this request returns no accounts (or stalls behind a slow
- * endpoint) with no useful answer. As one cold-boot step it must not block the
- * fall-through to the terminal `/sso` bounce. 3s bounds the wait while leaving
- * ample headroom for a genuine first-party `*.oxy.so` rotation round-trip.
- */
-const COOKIE_RESTORE_TIMEOUT = 3000;
-
 /**
  * Per-step fail-fast budget (ms) for the native shared-key cold-boot step
  * (`signInWithSharedIdentity`).
@@ -125,15 +77,14 @@ const SHARED_KEY_SIGNIN_TIMEOUT = 8000;
 /**
  * HARD overall deadline (ms) for the entire cold-boot step loop —
  * defense-in-depth so a single non-settling step can NEVER hang auth resolution
- * forever (the production regression: a `navigator.credentials.get()` that
- * ignored its abort signal left the `fedcm-silent` step's promise unsettled, so
- * `runColdBoot` never advanced to the terminal `/sso` bounce and auth hung
- * indefinitely).
+ * forever (the production regression this guards against: a browser silent
+ * credential/iframe probe that ignored its own abort signal left a step's
+ * promise unsettled, so `runColdBoot` never advanced to the terminal `/sso`
+ * bounce and auth hung indefinitely).
  *
  * Every step ALREADY bounds its own network work (the stored-session bearer
- * validation at 8s, the silent iframe at `SILENT_IFRAME_TIMEOUT`, the refresh
- * cookie at `COOKIE_RESTORE_TIMEOUT`, FedCM silent at `FEDCM_SILENT_TIMEOUT`
- * plus its hard settle). On a healthy load the FIRST recovering step wins in a
+ * validation at 8s, the silent iframe at `SILENT_IFRAME_TIMEOUT` plus its hard
+ * settle). On a healthy load the FIRST recovering step wins in a
  * single round-trip (1–3s) and the chain short-circuits long before this fires.
  * This budget only trips when one of those per-step bounds regresses.
  *
@@ -150,6 +101,23 @@ const SHARED_KEY_SIGNIN_TIMEOUT = 8000;
  */
 const COLD_BOOT_OVERALL_DEADLINE = 20000;
 
+/**
+ * How long cold boot WAITS for the post-ladder SessionClient handoff
+ * (`addCurrentAccount` + `start` + `syncFromClient`) before it resolves auth
+ * and stops blocking. Once a ladder step planted a token the user is already
+ * authenticated — the handoff only populates the multi-account set and the
+ * server-authoritative active account, and those also arrive via the socket
+ * subscription wired in `useEffect`. So on a slow/unresponsive backend we stop
+ * AWAITING the handoff here (it keeps running in the background and projects
+ * when it lands) rather than delaying `markAuthResolved` — otherwise the two
+ * sequential `HttpService`-bounded REST calls could push auth resolution up to
+ * ~10s past the ladder's own budget, reintroducing the exact spinner-stall
+ * `COLD_BOOT_OVERALL_DEADLINE` exists to prevent. On the normal fast path the
+ * handoff completes well within this, so the correct account shows with no
+ * flash.
+ */
+const SESSION_HANDOFF_DEADLINE = 6000;
+
 /**
  * Per-session soft timeout (ms) for the parallel stored-session validation in
  * `restoreStoredSession`. Each `validateSession` call races against this timer
@@ -408,9 +376,10 @@ const OxyProvider = ({
   // hooks below. But it is `null` for a brief window after mount while
   // `createPlatformStorage()` resolves (a microtask on web; a dynamic
   // `import()` on native). Any persistence path that fires during that window
-  // — e.g. an interactive FedCM sign-in the instant the screen mounts — would
-  // read `storage === null` and SILENTLY skip writing the session, leaving the
-  // user signed-in in-memory but with nothing to restore on reload.
+  // — e.g. an interactive password sign-in the instant the screen mounts —
+  // would read `storage === null` and SILENTLY skip writing the session,
+  // leaving the user signed-in in-memory but with nothing to restore on
+  // reload.
   //
   // To make persistence robust regardless of timing we ALSO expose the storage
   // as an awaitable promise (`getReadyStorage`). Persistence code awaits the
@@ -514,10 +483,8 @@ const OxyProvider = ({
     setActiveSessionId,
     updateSessions,
     switchSession,
-    refreshSessions,
     clearSessionState,
-    saveActiveSessionId,
-    trackRemovedSession
+    saveActiveSessionId
   } = (0, _useSessionManagement.useSessionManagement)({
     oxyServices,
     storage,
@@ -534,6 +501,139 @@ const OxyProvider = ({
     setTokenReady,
     queryClient
   });
+
+  // Session-sync integration layer (Fase 3-A -> 3-B). Built ONCE per
+  // `oxyServices` instance via a lazy ref (mirrors the `oxyServicesRef`
+  // pattern above) so the underlying `SessionClient` — and its socket
+  // connection, once started — is never recreated across renders.
+  //
+  // ADDITIVE + INERT for this task: `client.start()` is NOT called here (that
+  // is Task 2's job, which also retires the 8-step cold boot below). Until
+  // then `client.getState()` never advances past `null`, so `syncFromClient`
+  // is a guaranteed no-op in production — the existing cold-boot-driven state
+  // remains the sole authority. The wiring exists so the projection can be
+  // exercised in isolation against a controlled client before the authority
+  // flip.
+  const sessionClientPairRef = (0, _react.useRef)(null);
+  if (!sessionClientPairRef.current) {
+    sessionClientPairRef.current = (0, _index.createSessionClient)(oxyServices);
+  }
+  const {
+    client: sessionClient,
+    host: sessionClientHost
+  } = sessionClientPairRef.current;
+
+  // Cold-boot registration dedup (Task 5). `handleWebSSOSession` (declared
+  // below) is the single commit funnel for every web ladder step that mints a
+  // session (`sso-return`, `shared-key-signin`, `silent-iframe`) — it registers
+  // the recovered account into the device set
+  // itself (`sessionClient.addCurrentAccount()`). The cold-boot post-ladder
+  // handoff ALSO registers, but only as a FALLBACK for the `stored-session`
+  // step, which commits through a completely different path
+  // (`switchSessionRef`) and never touches `sessionClient` on its own. This
+  // ref lets the handoff detect "did a ladder step already register this
+  // boot?" and skip a redundant second `POST /session/device/add`. Reset at
+  // the start of every cold-boot pass.
+  const registeredDuringBootRef = (0, _react.useRef)(false);
+
+  // Projects `client.getState()` onto the exposed `sessions` / `activeSessionId`
+  // / `user` via the SAME setters the existing cold-boot/session-management
+  // paths use. This is the SOLE authority for both a locally-initiated mutation
+  // (switch/logout resolving here) AND a REMOTELY-pushed `session_state` (the
+  // `device:<deviceId>` socket owned by `client.start()`, subscribed to below) —
+  // there is no per-domain `useSessionSocket` anymore.
+  //
+  // GAP FIX (Task 4): when the pushed/bootstrapped state reports ZERO device
+  // accounts, this device has been fully signed out — either by the LOCAL
+  // `logout()`/`logoutAll()` mutation (which also runs its own explicit
+  // cleanup) or, just as importantly, by a REMOTE actor (another tab/device
+  // removing the last session, or an admin revoking every device account)
+  // pushing that same empty state over the socket. The prior per-domain
+  // `useSessionSocket` forced a local sign-out in this situation
+  // (`triggerLocalSignOut`); without an equivalent here a remote full sign-out
+  // would leave `user`/`isAuthenticated`/the bearer token stale until the next
+  // 401. Route through the SAME `clearSessionState()` a local full sign-out
+  // uses (authStore reset, token clear, query-cache clear, storage clear) —
+  // idempotent with the local-logout caller's own explicit call.
+  //
+  // DELIBERATE-SIGN-OUT GUARD (Task 5): a zero-account state — however it
+  // arrived — is just as terminal as a local `logout()`/`logoutAll()`, so it
+  // sets the SAME durable "deliberately signed out" flag (web-only,
+  // best-effort) that those two callers set directly. Without this, a remote
+  // full wipe would leave the flag unset, and the `silent-iframe` cold-boot
+  // step could silently re-mint a session from a still-live per-apex
+  // `fedcm_session` cookie right after this device was authoritatively signed
+  // out everywhere.
+  //
+  // REMOTE-SIGN-OUT SUPPRESSION FIX (review H1): the terminal `sso-bounce`
+  // cold-boot step is gated on the durable prior-session hint
+  // (`allowSsoBounce` = `hasPriorSession || hasLocalSession`), NOT on the
+  // deliberately-signed-out flag set above. Leaving that hint in place after a
+  // REMOTE full sign-out means the next reload still performs one terminal
+  // `/sso` establish bounce, which can silently re-mint a session from a
+  // still-live central `fedcm_session` — signing the user back in right after
+  // they were signed out everywhere. Clear the SAME cleanup set the LOCAL
+  // `logout()`/`logoutAll()` paths use (`useAuthOperations.ts`) — SSO bounce
+  // state + the prior-session hint — so a remote sign-out is indistinguishable
+  // from a local one to the next cold boot.
+  const syncFromClient = (0, _react.useCallback)(async () => {
+    const state = sessionClient.getState();
+    if (state === null) {
+      // INERT: no session state has been bootstrapped (client.start() has not
+      // run). Never overwrite the existing cold-boot-driven state.
+      return;
+    }
+    if (state.accounts.length === 0) {
+      sessionClientHost.setCurrentAccountId(null);
+      if ((0, _useWebSSO.isWebBrowser)()) {
+        (0, _activeAuthuser.markSignedOut)();
+      }
+      (0, _activeAuthuser.clearSsoBounceState)();
+      (0, _useAuthOperations.clearPriorSessionHintSafe)(clearPriorSessionHint, logger);
+      await clearSessionState();
+      return;
+    }
+    // LAST-WRITE-WINS GUARD (review I3): `syncFromClient` is called
+    // concurrently — once per socket `notify()` push AND once per direct
+    // mutation call — and each invocation captures `state` before an async
+    // profile fetch (`getUsersByIds`). `SessionClient`'s own state is
+    // monotonic by revision, but this projection previously was not: a
+    // SLOWER, OLDER fetch resolving AFTER a newer one would still apply its
+    // now-stale captured `state`, clobbering `user`/`sessions`/
+    // `activeSessionId` back to an outdated account. Capture the revision
+    // this fetch is FOR, then after the await, re-read the client's current
+    // state and bail if it has since moved past the captured revision — a
+    // fresher call has already applied (or will apply) the current truth.
+    const capturedRevision = state.revision;
+    const ids = (0, _index.accountIdsOf)(state);
+    let users = [];
+    try {
+      users = ids.length > 0 ? await oxyServices.getUsersByIds(ids) : [];
+    } catch (fetchError) {
+      // Invoked fire-and-forget from the socket `notify()` subscription, so a
+      // rejected profile fetch would surface as an unhandled rejection. Log and
+      // bail; the next `notify()`/mutation will re-project the current truth.
+      logger('Failed to resolve account profiles during syncFromClient', fetchError);
+      return;
+    }
+    const latest = sessionClient.getState();
+    if (!latest || latest.revision !== capturedRevision) {
+      return;
+    }
+    const usersById = new Map(users.map(resolvedUser => [resolvedUser.id, resolvedUser]));
+    updateSessions((0, _index.deviceStateToClientSessions)(latest, usersById));
+    setActiveSessionId((0, _index.activeSessionIdOf)(latest));
+    const activeUser = (0, _index.activeUserOf)(latest, usersById);
+    if (activeUser) {
+      loginSuccess(activeUser);
+    }
+    sessionClientHost.setCurrentAccountId(latest.activeAccountId);
+  }, [oxyServices, sessionClient, sessionClientHost, updateSessions, setActiveSessionId, loginSuccess, clearSessionState, clearPriorSessionHint, logger]);
+  (0, _react.useEffect)(() => {
+    return sessionClient.subscribe(() => {
+      void syncFromClient();
+    });
+  }, [sessionClient, syncFromClient]);
   const {
     signIn,
     logout,
@@ -541,7 +641,6 @@ const OxyProvider = ({
   } = (0, _useAuthOperations.useAuthOperations)({
     oxyServices,
     storage,
-    sessions,
     activeSessionId,
     setActiveSessionId,
     updateSessions,
@@ -549,6 +648,8 @@ const OxyProvider = ({
     clearSessionState,
     clearPriorSessionHint,
     switchSession,
+    sessionClient,
+    syncFromClient,
     applyLanguagePreference,
     onAuthStateChange,
     onError,
@@ -676,7 +777,7 @@ const OxyProvider = ({
   // init. Callers MUST invoke this BEFORE any work that can trigger a route
   // navigation (`onAuthStateChange`) — navigation can interrupt a still-pending
   // async write, which is exactly what once left `session_ids` empty after a
-  // successful sign-in. Shared by the FedCM/SSO path and the cold-boot
+  // successful sign-in. Shared by the SSO/silent-restore path and the cold-boot
   // refresh-cookie restore so both land the same durable record.
   const persistSessionDurably = (0, _react.useCallback)(async sessionId => {
     const readyStorage = await getReadyStorage();
@@ -695,7 +796,7 @@ const OxyProvider = ({
     // A session is now durably committed — set the returning-user hint so a
     // future cold boot whose local session has lapsed still gets ONE `/sso`
     // establish bounce (see `markPriorSessionHint`). Every web commit path
-    // (FedCM / silent iframe / SSO return / password / cookie restore) funnels
+    // (silent iframe / SSO return / password / cookie restore) funnels
     // through here, so this is the single chokepoint for the hint.
     await readyStorage.setItem(storageKeys.priorSession, '1');
   }, [getReadyStorage, logger, storageKeys.activeSessionId, storageKeys.sessionIds, storageKeys.priorSession]);
@@ -714,10 +815,10 @@ const OxyProvider = ({
   // Idempotent and monotonic via `authResolvedRef`: the first call wins and the
   // setters fire at most once, so the restore `finally` backstop becomes a no-op
   // once a commit site has already marked resolution. Called from EVERY place a
-  // user is actually committed (the FedCM/iframe/SSO path
-  // `handleWebSSOSession`, the cookie-restore path, and the stored-session path)
-  // so the common reload case unblocks the loading gate without sitting behind
-  // the remaining (now-skipped) cold-boot steps.
+  // user is actually committed (the iframe/SSO path
+  // `handleWebSSOSession` and the stored-session path) so the common reload
+  // case unblocks the loading gate without sitting behind the remaining
+  // (now-skipped) cold-boot steps.
   const markAuthResolved = (0, _react.useCallback)(() => {
     if (authResolvedRef.current) {
       return;
@@ -730,110 +831,13 @@ const OxyProvider = ({
   markAuthResolvedRef.current = markAuthResolved;
 
   // `handleWebSSOSession` is declared further down (it depends on values that
-  // are only available there). The FedCM/iframe cold-boot steps need to commit
+  // are only available there). The iframe/SSO cold-boot steps need to commit
   // a recovered session through it, so we route the call through a ref that is
   // populated once the callback exists. The ref is assigned synchronously on
   // every render before the cold-boot effect can fire (the effect is gated on
   // `storage` + `initialized`, both of which settle after first render).
   const handleWebSSOSessionRef = (0, _react.useRef)(null);
 
-  // Cold-boot session restore via the secure refresh cookies (web only).
-  //
-  // Calls `oxyServices.refreshAllSessions()` → `POST /auth/refresh-all` with
-  // `credentials: 'include'`. The server rotates every device-local
-  // `oxy_rt_${authuser}` cookie in parallel and returns one entry per valid
-  // account (Google-style multi-account).
-  //
-  // Active-account selection: the persisted `oxy_active_authuser` slot index
-  // wins when it matches a returned account; otherwise the lowest `authuser`
-  // is picked. JS never sees the refresh cookies (httpOnly).
-  //
-  // Returns `true` when at least one session was restored (caller short-
-  // circuits the bearer path); `false` on no signed-in accounts / any failure
-  // (caller proceeds unauthenticated through the existing flow — nothing is
-  // cleared).
-  const restoreViaRefreshCookie = (0, _react.useCallback)(async () => {
-    if (!(0, _useWebSSO.isWebBrowser)()) {
-      return false;
-    }
-    let snapshot;
-    try {
-      // Bound the refresh so a cross-domain/stalled call cannot hang the cold
-      // boot in front of the terminal `/sso` bounce (see COOKIE_RESTORE_TIMEOUT).
-      snapshot = await oxyServices.refreshAllSessions({
-        timeout: COOKIE_RESTORE_TIMEOUT
-      });
-    } catch (fetchError) {
-      // Offline / network error — fall through to the cached/stored-session flow.
-      if (__DEV__) {
-        _core.logger.debug('Refresh-all cookie restore network error (expected when offline)', {
-          component: 'OxyContext',
-          method: 'restoreViaRefreshCookie'
-        }, fetchError);
-      }
-      return false;
-    }
-    if (snapshot.accounts.length === 0) {
-      return false;
-    }
-
-    // Pick the active account: persisted authuser if it still matches a returned
-    // account, otherwise the lowest authuser (deterministic). The server has
-    // already sorted ascending so [0] is the lowest.
-    const activeAccount = (0, _silentSessionRestore.selectActiveRefreshAccount)(snapshot.accounts, (0, _activeAuthuser.readActiveAuthuser)());
-
-    // Plant the active access token. Sibling accounts' access tokens stay in
-    // the snapshot (the chooser can drive a per-account refresh via
-    // `refreshTokenViaCookie({authuser})` on switch).
-    oxyServices.httpService.setTokens(activeAccount.accessToken);
-
-    // Fetch the full user with the freshly planted token. The refresh-all
-    // payload includes a minimal user shape (id, username, name, avatar,
-    // email, color) — sufficient for the chooser but the auth store wants the
-    // canonical User document for downstream rendering.
-    let fullUser;
-    try {
-      fullUser = await oxyServices.getCurrentUser();
-    } catch (userError) {
-      // Token planted but profile fetch failed (e.g. transient network). Do
-      // not claim a restored session; fall through so the stored-session flow
-      // can retry. Leave the planted token in place — it is valid and harmless.
-      if (__DEV__) {
-        _core.logger.debug('Refresh-all cookie restore: getCurrentUser failed', {
-          component: 'OxyContext',
-          method: 'restoreViaRefreshCookie'
-        }, userError);
-      }
-      return false;
-    }
-
-    // Build a ClientSession per returned account so the multi-session store
-    // reflects every device-local slot, not just the active one. The active
-    // account is flagged `isCurrent: true`.
-    const now = new Date();
-    const clientSessions = snapshot.accounts.map(account => ({
-      sessionId: account.sessionId,
-      deviceId: '',
-      expiresAt: account.expiresAt || new Date(now.getTime() + DEFAULT_SESSION_VALIDITY_MS).toISOString(),
-      lastActive: now.toISOString(),
-      userId: account.user?.id,
-      isCurrent: account.sessionId === activeAccount.sessionId,
-      authuser: account.authuser
-    }));
-    updateSessionsRef.current(clientSessions, {
-      merge: true
-    });
-    setActiveSessionIdRef.current(activeAccount.sessionId);
-    (0, _activeAuthuser.writeActiveAuthuser)(activeAccount.authuser);
-    await persistSessionDurably(activeAccount.sessionId);
-    loginSuccessRef.current(fullUser);
-    // A session is now committed — unblock the auth-resolution gate immediately
-    // rather than waiting for `runColdBoot` to return (idempotent).
-    markAuthResolvedRef.current();
-    onAuthStateChangeRef.current?.(fullUser);
-    return true;
-  }, [oxyServices, persistSessionDurably]);
-
   // Native (and offline) stored-session restore — the ONLY restore path that
   // runs on React Native, and the web fallback when no cross-domain step won.
   //
@@ -848,8 +852,23 @@ const OxyProvider = ({
     const storedSessionIdsJson = await storage.getItem(storageKeys.sessionIds);
     const storedSessionIdsFromStorage = storedSessionIdsJson ? JSON.parse(storedSessionIdsJson) : [];
     let storedActiveSessionId = await storage.getItem(storageKeys.activeSessionId);
+    // OPTIONAL HINT ONLY (no longer a gate). Nothing writes the active-`authuser`
+    // marker since the SessionClient cutover (`writeActiveAuthuser` was deleted),
+    // so it is `null` on every fresh install; when a legacy value is present it
+    // is used purely to backfill `clientSession.authuser` for the active session
+    // below. It MUST NOT decide whether restore is attempted — see the guard.
     const storedActiveAuthuser = (0, _useWebSSO.isWebBrowser)() ? (0, _activeAuthuser.readActiveAuthuser)() : null;
-    if ((0, _useWebSSO.isWebBrowser)() && !oxyServices.getAccessToken() && (storedActiveSessionId === null || storedActiveAuthuser === null)) {
+
+    // On web with no in-memory bearer, bail ONLY when there is genuinely nothing
+    // to restore — neither a stored active id NOR any stored session ids. A
+    // surviving `sessionIds` list (e.g. the active-id key was removed after a
+    // server-side revocation while sibling sessions remain) MUST still be
+    // validated over the network and have a valid session elected as active
+    // below. The old guard also required the deleted `activeAuthuser` marker,
+    // which since the cutover is never written — that made EVERY web reload
+    // whose local bearer had lapsed bail before any validation. Native always
+    // proceeds (it plants the shared KeyManager bearer next).
+    if ((0, _useWebSSO.isWebBrowser)() && !oxyServices.getAccessToken() && storedActiveSessionId === null && storedSessionIdsFromStorage.length === 0) {
       return false;
     }
     const nativeSharedSession = !(0, _useWebSSO.isWebBrowser)() ? await _core.KeyManager.getSharedSession().catch(() => null) : null;
@@ -946,23 +965,59 @@ const OxyProvider = ({
       } catch (switchError) {
         // Silently handle expected errors (invalid sessions, timeouts, network issues)
         if ((0, _errorHandlers.isInvalidSessionError)(switchError)) {
+          // The stored active id was rejected server-side. Clear it and drop the
+          // dead session from the local view, then FALL THROUGH to the election
+          // below to promote a surviving valid session — a stale/removed active
+          // marker must not strand the other still-valid accounts.
           await storage.removeItem(storageKeys.activeSessionId);
-          updateSessionsRef.current(validSessions.filter(session => session.sessionId !== storedActiveSessionId), {
+          validSessions = validSessions.filter(session => session.sessionId !== storedActiveSessionId);
+          updateSessionsRef.current(validSessions, {
             merge: false,
             preserveSessionIds: unvalidatedSessionIds
           });
           // Don't log expected session errors during restoration
         } else if ((0, _errorHandlers.isTimeoutOrNetworkError)(switchError)) {
-          // Timeout/network error - non-critical, don't block
+          // Timeout/network — the stored active session may still be valid; we
+          // just could not confirm it. Do NOT elect a different session (that
+          // could switch accounts under the user); leave restore to a retry / the
+          // remaining cold-boot steps.
           if (__DEV__) {
             _core.logger.debug('Active session validation timeout (expected when offline)', {
               component: 'OxyContext',
               method: 'restoreStoredSession'
             }, switchError);
           }
+          return false;
         } else {
-          // Only log unexpected errors
+          // Only log unexpected errors, and do not elect on an ambiguous failure.
           logger('Active session validation error', switchError);
+          return false;
+        }
+      }
+    }
+
+    // Election fallback. Reached when there is no usable stored active id —
+    // either it was never persisted (e.g. removed after a server-side revocation
+    // while sibling sessions survived) or it was just rejected as invalid above.
+    // Promote the FIRST validated session to active and commit it through the
+    // same `switchSession` path. The server owns which account is truly active,
+    // so any valid session is a safe provisional active — the post-restore
+    // SessionClient handoff reconciles the real active account immediately after.
+    const electedSession = validSessions[0];
+    if (electedSession) {
+      try {
+        await switchSessionRef.current(electedSession.sessionId);
+        await storage.setItem(storageKeys.activeSessionId, electedSession.sessionId);
+        await storage.setItem(storageKeys.priorSession, '1');
+        markAuthResolvedRef.current();
+        return true;
+      } catch (electionError) {
+        // Activation requires an in-memory bearer on web; without one (a plain
+        // web reload) the switch throws and recovery defers to the cross-domain
+        // cold-boot steps. Invalid/timeout/network are expected here — surface
+        // only genuinely unexpected failures.
+        if (!(0, _errorHandlers.isInvalidSessionError)(electionError) && !(0, _errorHandlers.isTimeoutOrNetworkError)(electionError)) {
+          logger('Elected session activation error', electionError);
         }
       }
     }
@@ -1037,21 +1092,31 @@ const OxyProvider = ({
   // web-only step is gated by `isWebBrowser()`, so on native ONLY
   // `stored-session` runs.
   //
-  // Order (web): SSO return → stored session → FedCM silent
-  // (central) → silent iframe (per-apex, the durable reload path) → cookie
-  // restore → SSO bounce (terminal).
+  // Order (web): SSO return → stored session → shared-key sign-in (native
+  // only, disabled here) → silent iframe (per-apex, the durable reload path)
+  // → SSO bounce (terminal). This is a pure TOKEN-ACQUISITION ladder — it
+  // mints the first per-domain access token by whichever means recovers one
+  // fastest. Once a token is acquired (or the ladder exhausts), the
+  // SERVER-authoritative `SessionClient` takes over: `addCurrentAccount` +
+  // `start` bootstrap the device session set and multi-account/active-account
+  // state from `GET /session/device/state`, so WHICH account is active is
+  // decided server-side, not by a client-persisted slot. There is no oxy_rt
+  // refresh-cookie restore step in this ladder, and no FedCM step — FedCM was
+  // removed from the client sign-in/cold-boot path entirely (Chrome-only, and
+  // its fast/silent failure mode combined with a caller's auth-guard effect
+  // could re-trigger sign-in in a tight loop; see `CrossDomainAuth`'s doc
+  // comment in `@oxyhq/core`).
   //
-  // LATENCY (FIX A): `stored-session` runs BEFORE the slow no-redirect probes
-  // (`fedcm-silent`, `silent-iframe`, `cookie-restore`). On a normal reload the
-  // local bearer validates in one round-trip and wins, so `runColdBoot`
-  // short-circuits and never sits through those probes' timeouts (the prior
-  // serial sum was a ~20-30s stall). `sso-return` MUST stay first — it consumes
-  // the URL fragment before anything can strip it. On a
-  // first visit with no local session, `stored-session` skips and the
-  // cross-domain fallback chain (fedcm → iframe → cookie → sso-bounce) runs
-  // exactly as before; the per-apex silent iframe still restores a durable
-  // cross-domain session on reload WITHOUT a top-level bounce, so when it wins
-  // `sso-bounce` never fires (no flash, no loop).
+  // LATENCY (FIX A): `stored-session` runs BEFORE the slow no-redirect
+  // `silent-iframe` probe. On a normal reload the local bearer validates in
+  // one round-trip and wins, so `runColdBoot` short-circuits and never sits
+  // through that probe's timeout. `sso-return` MUST stay first — it consumes
+  // the URL fragment before anything can strip it. On a first visit with no
+  // local session, `stored-session` skips and the cross-domain fallback chain
+  // (silent-iframe → sso-bounce) runs exactly as before; the per-apex silent
+  // iframe still restores a durable cross-domain session on reload WITHOUT a
+  // top-level bounce, so when it wins `sso-bounce` never fires (no flash, no
+  // loop).
   // Order (native): stored session only (every web-only step is disabled
   // off-browser).
   const restoreSessionsFromStorage = (0, _react.useCallback)(async () => {
@@ -1059,18 +1124,18 @@ const OxyProvider = ({
       return;
     }
     setTokenReady(false);
+    // Fresh per-boot flag — see the declaration comment above `sessionClient`.
+    registeredDuringBootRef.current = false;
     const commitWebSession = handleWebSSOSessionRef.current;
-    const silentKey = silentColdBootKey(oxyServices);
-    const fedcmSupported = (0, _useWebSSO.isWebBrowser)() && oxyServices.isFedCMSupported?.() === true;
 
     // FIX-B precondition flag: set true the instant the (now-earlier)
-    // `stored-session` step recovers a local bearer session. The slow web-only
-    // probes (`fedcm-silent`, `silent-iframe`) AND `enabled` on `!storedSessionRestored`
-    // so they are explicitly skipped once a local session won. `runColdBoot`
+    // `stored-session` step recovers a local bearer session. The slow
+    // web-only `silent-iframe` probe is `enabled` on `!storedSessionRestored`
+    // so it is explicitly skipped once a local session won. `runColdBoot`
     // already short-circuits on the first `{kind:'session'}`, so on a winning
-    // reload those `enabled` bodies are never even reached — this flag makes the
+    // reload that `enabled` body is never even reached — this flag makes the
     // intent explicit and is redundant-safe. On a first-visit-no-local-session,
-    // `stored-session` skips, this stays false, and the probes run as before.
+    // `stored-session` skips, this stays false, and the probe runs as before.
     let storedSessionRestored = false;
 
     // FIX-B smart-gate input: has this device/app EVER had a signed-in Oxy
@@ -1093,52 +1158,16 @@ const OxyProvider = ({
       }
     }
 
-    // LAST-ACTIVE-ACCOUNT priority (web multi-account). When the user has an
-    // explicit persisted active slot (`oxy_active_authuser`, written on every
-    // device sign-in / account SWITCH / cookie restore), the multi-account
-    // refresh-cookie restore is the ONLY cold-boot step that honors WHICH slot
-    // was last active — `restoreViaRefreshCookie` selects it via
-    // `selectActiveRefreshAccount(accounts, readActiveAuthuser())`. The
-    // `fedcm-silent` and per-apex `silent-iframe` steps only ever recover the
-    // PRIMARY central IdP session, so if either ran first they would clobber a
-    // switched (managed/org) account back to the primary on reload — the exact
-    // "switch is lost on reload" regression. So when a slot selection exists we
-    // run cookie-restore BEFORE those probes (and disable the later duplicate).
-    //
-    // Read ONCE here (synchronously usable by the step `enabled` gates below).
-    // It is non-null ONLY on first-party web apps that persist the slot. Both the
-    // device sign-in/switch paths AND `handleWebSSOSession` (FedCM/SSO/credentials
-    // commit funnel) now persist it — but only when the session genuinely joined
-    // the device set: `establishDeviceRefreshSlot` returns an `authuser` ONLY on
-    // first-party web (same registrable apex as the API), so a cross-apex RP never
-    // writes a phantom slot and native has no localStorage. Both therefore keep
-    // their existing order untouched. The earlier `stored-session` step still runs
-    // first (FIX-A latency), and when a slot exists but its cookies have all
-    // lapsed, cookie-restore simply returns no accounts and the chain falls through
-    // to the cross-domain fallbacks exactly as before.
-    const prioritizeMultiAccount = (0, _useWebSSO.isWebBrowser)() && (0, _activeAuthuser.readActiveAuthuser)() !== null;
-
-    // DELIBERATELY-SIGNED-OUT gate (web): when the user pressed "Sign out", any
-    // credential that can silently re-mint a session may still be live on the
-    // next reload — the central IdP session (FedCM credential association /
-    // per-apex `fedcm_session` cookie) AND the device refresh cookies. Since
-    // PR #455 the PRIMARY web session also joins the `oxy_rt_<authuser>` device
-    // set, so the un-gated cookie-restore steps would `refresh-all` that still-
-    // present cookie and sign the user back in without intent — exactly the
-    // "sign-out is silently undone" regression. So this flag gates EVERY
-    // AUTOMATIC silent-restore cold-boot step: `stored-session`,
-    // `cookie-restore-active`, `fedcm-silent`, `silent-iframe`, and
-    // `cookie-restore`. The gate — not a cookie wipe — is the authority: the
-    // account may stay "known" for a fast deliberate re-sign-in, but no step
-    // restores it silently while the flag is set. Read the durable flag ONCE here
-    // (synchronously usable by every step `enabled` gate). Any deliberate sign-in
-    // (password, FedCM, account switch, device claim) clears it, so there is no
-    // "stuck signed out" state. The `sso-bounce` step needs no extra gate: it is
-    // already self-suppressed after sign-out (its `hasPriorSession` hint is
-    // cleared). `sso-return` is NOT gated — it commits the result of a deliberate
-    // top-level `/sso` bounce the user just initiated. `shared-key-signin` is
-    // native-only and the flag never sets on native (`markSignedOut` no-ops
-    // off-web), so its gate would be moot; it is left untouched.
+    // DELIBERATELY-SIGNED-OUT gate (web): when the user pressed "Sign out", the
+    // per-apex `fedcm_session` cookie can still be live, so the AUTOMATIC
+    // `silent-iframe` step below would re-mint a session on the very next cold
+    // boot and sign the user back in without intent. Read the durable flag
+    // ONCE here (synchronously usable by the step `enabled` gate) and skip
+    // that step while it is set. Any deliberate sign-in clears it. The
+    // `sso-bounce` step is already self-suppressed after sign-out (its
+    // `hasPriorSession` hint is cleared), and the local `stored-session`
+    // restore step is unaffected — a deliberate sign-out clears those
+    // credentials anyway.
     const silentRestoreBlocked = (0, _activeAuthuser.isSilentRestoreSuppressed)();
     try {
       const outcome = await (0, _core.runColdBoot)({
@@ -1160,28 +1189,22 @@ const OxyProvider = ({
             };
           }
         }, {
-          // 2) Stored-session bearer restore. Runs on ALL platforms EXCEPT when
-          // the deliberately-signed-out flag is set (web only — it never sets on
-          // native, so native still always reaches exactly this step, its ONLY
-          // restore path). This is also the common WEB reload winner.
+          // 2) Stored-session bearer restore. NO `enabled` gate — runs on ALL
+          // platforms. This is native's ONLY restore path (every web-only step
+          // is disabled off-browser, so native reaches exactly this) AND the
+          // common WEB reload winner.
           //
-          // SIGNED-OUT GATE: after a deliberate full sign-out the stored session
-          // state is cleared, so this would normally skip anyway — but the gate
-          // makes that authoritative rather than incidental, so no residual
-          // stored token can silently restore while the user is signed out.
-          //
-          // ORDERING (FIX A): this step runs BEFORE the slow web-only
-          // probes (`fedcm-silent`, `silent-iframe`, `cookie-restore`). On a
-          // normal reload the local bearer validates in one round-trip and
-          // wins; `runColdBoot` then short-circuits and never even evaluates
-          // the slow no-redirect probes that would otherwise time out (the
-          // ~20-30s serial stall). The `sso-return` step stays AHEAD of this
-          // one — it must consume the URL fragment before any
-          // later step (or anything else) strips it. On a first visit with no
-          // local session this step skips and the cross-domain fallback chain
-          // (fedcm → iframe → cookie → sso-bounce) runs exactly as before.
+          // ORDERING (FIX A): this step now runs BEFORE the slow web-only
+          // `silent-iframe` probe. On a normal reload the local bearer
+          // validates in one round-trip and wins; `runColdBoot`
+          // then short-circuits and never even evaluates the slow
+          // no-redirect probe that would otherwise time out (the ~20-30s
+          // serial stall). The `sso-return` step stays AHEAD of this one —
+          // it must consume the URL fragment before any later step (or
+          // anything else) strips it. On a first visit with no local
+          // session this step skips and the cross-domain fallback chain
+          // (silent-iframe → sso-bounce) runs exactly as before.
           id: 'stored-session',
-          enabled: () => !silentRestoreBlocked,
           run: async () => {
             const restored = await restoreStoredSession();
             if (restored) {
@@ -1251,66 +1274,7 @@ const OxyProvider = ({
             };
           }
         }, {
-          // 2.75) LAST-ACTIVE multi-account restore (WEB, prioritized). Runs
-          // ONLY when an explicit persisted slot selection exists
-          // (`prioritizeMultiAccount`) — i.e. the user previously signed in or
-          // SWITCHED accounts on this first-party app. It runs BEFORE the
-          // `fedcm-silent` / `silent-iframe` probes (which only ever recover the
-          // PRIMARY central session) so a switched managed/org account survives
-          // reload instead of being clobbered back to the primary. The restore
-          // itself is the SAME `restoreViaRefreshCookie` as the terminal-tier
-          // step below: it rotates every device-local `oxy_rt_<authuser>` cookie
-          // and picks the persisted slot via `selectActiveRefreshAccount`,
-          // committing it (token + state + durable persistence + `markAuthResolved`).
-          // When no slot is persisted this is disabled and the original order is
-          // unchanged; when the slot's cookies have lapsed it returns no accounts
-          // and the chain falls through to the cross-domain fallbacks below.
-          //
-          // SIGNED-OUT GATE: since PR #455 the primary's `oxy_rt` slot survives a
-          // deliberate sign-out, so without this gate `refresh-all` would re-mint
-          // and silently re-log-in the user on reload. The flag is cleared by any
-          // deliberate sign-in (including an account SWITCH, which also writes the
-          // new active slot), so the switch-survives-reload path is unaffected.
-          id: 'cookie-restore-active',
-          enabled: () => prioritizeMultiAccount && !silentRestoreBlocked,
-          run: async () => {
-            const restored = await restoreViaRefreshCookie();
-            return restored ? {
-              kind: 'session',
-              session: true
-            } : {
-              kind: 'skip'
-            };
-          }
-        }, {
-          // 3) FedCM silent reauthn (Chrome) against the CENTRAL IdP
-          // (auth.oxy.so). `silentSignInWithFedCM` plants the access token
-          // internally; we commit the returned session via
-          // `handleWebSSOSession`. Guarded so it fires at most once per page
-          // load across remounts. This is an enhancement layered above the
-          // opaque-code bounce: when it succeeds the bounce never fires.
-          //
-          // FIX-B: additionally skipped when the earlier `stored-session` step
-          // already recovered a local session — the probe cannot improve on a
-          // valid local bearer, and skipping it avoids the silent round-trip.
-          id: 'fedcm-silent',
-          enabled: () => !storedSessionRestored && !silentRestoreBlocked && fedcmSupported && !servicesSilentAttempted.has(silentKey),
-          run: async () => {
-            servicesSilentAttempted.add(silentKey);
-            const session = await oxyServices.silentSignInWithFedCM?.();
-            if (!session || !commitWebSession) {
-              return {
-                kind: 'skip'
-              };
-            }
-            await commitWebSession(session);
-            return {
-              kind: 'session',
-              session: true
-            };
-          }
-        }, {
-          // 4) First-party silent iframe at the PER-APEX IdP — the DURABLE
+          // 3) First-party silent iframe at the PER-APEX IdP — the DURABLE
           // cross-domain reload-restore path. The durable session lives as a
           // first-party `fedcm_session` cookie on `auth.<rp-apex>` (e.g.
           // `auth.mention.earth`), established during the `/sso` bounce's
@@ -1357,39 +1321,7 @@ const OxyProvider = ({
             };
           }
         }, {
-          // 5) Refresh-cookie restore (first-party only). On `*.oxy.so` the
-          // httpOnly `oxy_rt_${n}` cookies ride along and resurrect every
-          // device-local slot. On a cross-domain RP (mention.earth, …) the
-          // cookie is `Domain=oxy.so` so it never reaches `api.<apex>` —
-          // `refreshAllSessions` returns `{accounts:[]}` and this skips. That
-          // is correct; cross-domain restore is handled by the SSO bounce.
-          // FIX-D: `restoreViaRefreshCookie` bounds the request with
-          // `COOKIE_RESTORE_TIMEOUT` so a cross-domain stall cannot hang here.
-          //
-          // Disabled when `prioritizeMultiAccount` already ran the
-          // `cookie-restore-active` step above (an explicit persisted slot) — that
-          // earlier step is the identical restore, so this terminal-tier copy
-          // would be a redundant second `refreshAllSessions`. It still runs in the
-          // common no-persisted-slot case (e.g. first visit to a first-party app
-          // whose central refresh cookies already exist).
-          //
-          // SIGNED-OUT GATE (same rationale as `cookie-restore-active`): the
-          // primary's `oxy_rt` slot survives a deliberate sign-out (PR #455), so
-          // this must be skipped while the signed-out flag is set or it would
-          // silently re-restore the primary on reload.
-          id: 'cookie-restore',
-          enabled: () => (0, _useWebSSO.isWebBrowser)() && !prioritizeMultiAccount && !silentRestoreBlocked,
-          run: async () => {
-            const restored = await restoreViaRefreshCookie();
-            return restored ? {
-              kind: 'session',
-              session: true
-            } : {
-              kind: 'skip'
-            };
-          }
-        }, {
-          // 6) SSO bounce (TERMINAL, web only, at most once). No local session
+          // 4) SSO bounce (TERMINAL, web only, at most once). No local session
           // was found by any step above. Top-level navigate to the central
           // `auth.oxy.so/sso?prompt=none` so the IdP can either mint a session
           // (returning an opaque code we exchange on the callback) or report
@@ -1466,9 +1398,9 @@ const OxyProvider = ({
             }, error);
           }
         },
-        // Defense-in-depth: a single step whose promise never settles (the
-        // production FedCM-silent hang) can no longer block the chain forever.
-        // On expiry the runner keeps iterating to the terminal `sso-bounce`
+        // Defense-in-depth: a single step whose promise never settles can no
+        // longer block the chain forever. On expiry the runner keeps iterating
+        // to the terminal `sso-bounce`
         // step so a genuine no-local-session visit still reaches the
         // cross-domain `/sso` fallback; the `finally` backstop flips
         // `authResolved` regardless. See `COLD_BOOT_OVERALL_DEADLINE`.
@@ -1488,6 +1420,76 @@ const OxyProvider = ({
           method: 'restoreSessionsFromStorage'
         });
       }
+
+      // TOKEN LADDER → SESSIONCLIENT AUTHORITY HANDOFF. The steps above are
+      // ONLY a token-acquisition ladder — they mint the first per-domain
+      // access token by whichever means recovers one fastest. Once a session
+      // is known (either this cold boot committed one via the ladder, or an
+      // access token is already held in memory — e.g. a prior render already
+      // planted it), hand off to the server-authoritative `SessionClient`:
+      // `addCurrentAccount` registers this recovered account+session into the
+      // server `DeviceSession` (derives identity from the bearer), `start`
+      // bootstraps the full device-session state (server `activeAccountId` +
+      // `activeToken`) and connects the realtime socket, and `syncFromClient`
+      // projects that state onto the exposed `sessions`/`activeSessionId`/
+      // `user`. This is what lets a switched (managed/org) account survive
+      // reload: the SERVER, not a client-persisted slot, owns which account is
+      // active. Never call the client when no session was acquired — an
+      // anonymous visitor must stay logged out. Failures are logged and
+      // swallowed; they must never throw out of cold boot.
+      //
+      // `addCurrentAccount` is SKIPPED when `registeredDuringBootRef` is
+      // already `true` — every ladder step except `stored-session` commits
+      // through `handleWebSSOSession`, which registers the account itself
+      // (see its own `sessionClient.addCurrentAccount()` call). Without this
+      // guard a winning `sso-return` / `shared-key-signin` / `silent-iframe`
+      // step would register the SAME account twice
+      // (`POST /session/device/add` called back-to-back). `start()` and
+      // `syncFromClient()` still always run — `start()` is idempotent
+      // (no-ops once already started) and is what connects the realtime
+      // socket for the first time.
+      if (outcome.kind === 'session' || oxyServices.getAccessToken()) {
+        // Self-contained: never throws (own try/catch), so it is safe to let it
+        // outlive the race below and finish in the background if the deadline
+        // trips — the socket subscription then projects the state when it lands.
+        const handoff = (async () => {
+          try {
+            if (!registeredDuringBootRef.current) {
+              // Nested guard: registering this account into the device set is
+              // best-effort. If it throws, `start()` must STILL run so the
+              // realtime socket connects and state projects — cold boot
+              // re-registers the account into the device set on the next load.
+              try {
+                await sessionClient.addCurrentAccount();
+              } catch (addAccountErr) {
+                _core.logger.warn('cold-boot: addCurrentAccount failed; continuing to start()', {
+                  component: 'OxyContext',
+                  method: 'restoreSessionsFromStorage'
+                }, addAccountErr);
+              }
+            }
+            await sessionClient.start();
+            await syncFromClient();
+          } catch (startErr) {
+            _core.logger.warn('cold-boot: SessionClient start failed', {
+              component: 'OxyContext',
+              method: 'restoreSessionsFromStorage'
+            }, startErr);
+          }
+        })();
+        // Bound how long auth resolution waits for the handoff (see
+        // `SESSION_HANDOFF_DEADLINE`): the token is already planted, so on a
+        // slow backend we proceed to `markAuthResolved` and let the handoff
+        // complete asynchronously rather than stalling the spinner.
+        let handoffDeadlineId;
+        await Promise.race([handoff, new Promise(resolve => {
+          handoffDeadlineId = setTimeout(resolve, SESSION_HANDOFF_DEADLINE);
+        })]).finally(() => {
+          if (handoffDeadlineId !== undefined) {
+            clearTimeout(handoffDeadlineId);
+          }
+        });
+      }
     } catch (error) {
       if (__DEV__) {
         _core.logger.error('Auth init error', error instanceof Error ? error : new Error(String(error)), {
@@ -1506,7 +1508,7 @@ const OxyProvider = ({
       // `authResolved` finally flip. Monotonic — never reverts on later restores.
       markAuthResolved();
     }
-  }, [oxyServices, storage, storageKeys.priorSession, restoreViaRefreshCookie, restoreStoredSession, runSsoReturn, markAuthResolved]);
+  }, [oxyServices, storage, storageKeys.priorSession, restoreStoredSession, runSsoReturn, markAuthResolved, sessionClient, syncFromClient]);
   (0, _react.useEffect)(() => {
     if (!storage || initialized) {
       return;
@@ -1621,34 +1623,37 @@ const OxyProvider = ({
 
     // A committed web session re-enables automatic silent restore: clear the
     // durable "deliberately signed out" flag. This funnel is reached by deliberate
-    // sign-ins (password, interactive FedCM, `/sso` return) AND by the silent
+    // sign-ins (password, `/sso` return) AND by the silent
     // cold-boot steps — but those are GATED on the flag, so when it is set they
     // never run and never reach here; clearing is therefore only hit on a genuine
     // (re-)sign-in or when restore was already permitted, both correct.
     (0, _activeAuthuser.clearSignedOut)();
 
-    // Register this primary session in the device's first-party multi-account
-    // refresh-cookie set (web only). Every web primary-session restore funnels
-    // through here — FedCM silent (`/fedcm/exchange`), per-apex `/auth/silent`
-    // iframe, central `/sso` return, and keyless password sign-in. Of those, only
-    // a same-apex `/fedcm/exchange` plants an `oxy_rt_<authuser>` slot as a side
-    // effect; the cross-origin/credential-less restores (`/sso/exchange`,
-    // `/auth/silent` postMessage) cannot set an `api.oxy.so` cookie at all. So
-    // WITHOUT this call a web primary never joins the device set: `refresh-all`
-    // returns zero accounts, and account-switch persistence + the
-    // `cookie-restore-active` cold-boot step have no foundation. Calling the shared
-    // `POST /auth/session` primitive here makes EVERY primary participate in the
-    // set, re-plants the rotated token, and records the active `authuser` so the
-    // next cold boot's `cookie-restore-active` reconciles the persisted active
-    // (possibly switched) account instead of `fedcm-silent` clobbering it back to
-    // the primary. Best-effort: a `null` result (native / transient failure)
-    // leaves the in-session token untouched.
-    const primaryAuthuser = await oxyServices.establishDeviceRefreshSlot();
-    // A non-null slot is returned ONLY on first-party web (the helper gates on
-    // platform + same registrable apex), so recording the active slot here is safe
-    // and never writes a phantom authuser for a cross-apex RP or native.
-    if (typeof primaryAuthuser === 'number') {
-      (0, _activeAuthuser.writeActiveAuthuser)(primaryAuthuser);
+    // Register this recovered account+session into the server-authoritative
+    // device-session set. Every web primary-session restore funnels through
+    // here — per-apex `/auth/silent` iframe,
+    // central `/sso` return, and keyless password sign-in — and each of them
+    // needs the resulting account added to the device's `DeviceSession` doc so
+    // the sign-in persists across reload / other tabs / devices and the
+    // realtime `device:<deviceId>` socket has an account to track.
+    // `sessionClient.addCurrentAccount()` (`POST /session/device/add`) derives
+    // identity from the bearer this function just planted above;
+    // `syncFromClient()` reprojects the resulting server state onto the
+    // exposed sessions/activeSessionId/user. Best-effort: a failure here must
+    // NEVER fail the sign-in itself — cold boot re-registers this account into
+    // the device set on the next load regardless. `registeredDuringBootRef` is
+    // flipped on success so the cold-boot post-ladder handoff (which reaches
+    // every step, including this one) does not redundantly re-register the
+    // SAME account with a second `POST /session/device/add`.
+    try {
+      await sessionClient.addCurrentAccount();
+      registeredDuringBootRef.current = true;
+      await syncFromClient();
+    } catch (registrationError) {
+      _core.logger.warn('handleWebSSOSession: failed to register session into device set', {
+        component: 'OxyContext',
+        method: 'handleWebSSOSession'
+      }, registrationError);
     }
     const clientSession = {
       sessionId: session.sessionId,
@@ -1656,10 +1661,7 @@ const OxyProvider = ({
       expiresAt: session.expiresAt || new Date(Date.now() + DEFAULT_SESSION_VALIDITY_MS).toISOString(),
       lastActive: new Date().toISOString(),
       userId: session.user.id?.toString() ?? '',
-      isCurrent: true,
-      ...(typeof primaryAuthuser === 'number' ? {
-        authuser: primaryAuthuser
-      } : null)
+      isCurrent: true
     };
     updateSessions([clientSession], {
       merge: true
@@ -1673,7 +1675,7 @@ const OxyProvider = ({
     // because `onAuthStateChange` triggers a route navigation that can
     // interrupt/supersede a still-pending async write. Persisting first
     // guarantees the durable record lands; that is exactly what was missing
-    // when `oxy_session_session_ids` came back empty after a successful FedCM
+    // when `oxy_session_session_ids` came back empty after a successful SSO
     // sign-in (the user appeared logged in until reload, then had no session to
     // restore). `persistSessionDurably` awaits the READY storage instance rather
     // than reading the possibly-null `storage` state, so a sign-in fired the
@@ -1700,14 +1702,14 @@ const OxyProvider = ({
       fullUser = session.user;
     }
     loginSuccess(fullUser);
-    // A session is now committed (FedCM silent / per-apex iframe /
+    // A session is now committed (per-apex iframe /
     // SSO-return all funnel through here) — unblock the auth-resolution
     // gate immediately, ahead of the cold-boot chain returning (idempotent).
     markAuthResolvedRef.current();
     onAuthStateChange?.(fullUser);
-  }, [oxyServices, updateSessions, setActiveSessionId, loginSuccess, onAuthStateChange, persistSessionDurably]);
+  }, [oxyServices, updateSessions, setActiveSessionId, loginSuccess, onAuthStateChange, persistSessionDurably, sessionClient, syncFromClient]);
 
-  // Expose `handleWebSSOSession` to the cold-boot FedCM/iframe/SSO steps,
+  // Expose `handleWebSSOSession` to the cold-boot iframe/SSO steps,
   // which reference it through a ref because they are declared above this
   // callback. Assigned synchronously on every render so the ref is populated
   // before the cold-boot effect (gated on `storage`/`initialized`) can fire.
@@ -1715,7 +1717,7 @@ const OxyProvider = ({
 
   // Keyless native sign-in: username/email + password. The slimmed Accounts app
   // (which no longer holds a local identity key) uses this; it commits a
-  // successful session through the SAME `handleWebSSOSession` path FedCM / SSO
+  // successful session through the SAME `handleWebSSOSession` path SSO
   // use, so state, durable persistence, profile fetch, and `markAuthResolved`
   // all run identically. The API returns either a full session OR a two-factor
   // handoff (`{ twoFactorRequired, loginToken }`) — we surface the latter as a
@@ -1748,32 +1750,29 @@ const OxyProvider = ({
     };
   }, [oxyServices, handleWebSSOSession]);
 
-  // Cross-domain silent SSO is now owned by the `fedcm-silent` / `silent-iframe`
-  // cold-boot steps above (the ordered `runColdBoot` sequence). `useWebSSO`
-  // remains mounted for its module-level run-once guard and its interactive
-  // FedCM helpers, and as a bounded post-boot safety net: it can fire at most
-  // once per page load (its own module guard), and only AFTER cold boot has
-  // finished (`tokenReady`) with no user recovered. We deliberately keep
-  // `shouldTryWebSSO` as `tokenReady && !user && initialized` — it is NOT
-  // loosened; cold boot runs while `tokenReady` is false, so this never races
-  // the cold-boot silent step.
-  const shouldTryWebSSO = (0, _useWebSSO.isWebBrowser)() && tokenReady && !user && initialized;
-  (0, _useWebSSO.useWebSSO)({
-    oxyServices,
-    onSessionFound: handleWebSSOSession,
-    onError: error => {
-      if (__DEV__) {
-        _core.logger.debug('Web SSO check failed (non-critical)', {
-          component: 'OxyContext'
-        }, error);
-      }
-    },
-    enabled: shouldTryWebSSO
-  });
+  // Cross-domain silent SSO is owned ENTIRELY by the `silent-iframe` cold-boot
+  // step above (the ordered `runColdBoot` sequence) plus the terminal
+  // `sso-bounce` fallback. There is no post-boot safety net here: the FedCM
+  // silent post-boot retry that used to run via `useWebSSO` was removed along
+  // with the rest of the client FedCM surface (Chrome-only; see
+  // `CrossDomainAuth`'s doc comment in `@oxyhq/core` for the production
+  // incident that motivated the removal).
 
   // IdP session validation via lightweight iframe check
   // When user returns to tab, verify auth.oxy.so still has their session
   // If session is gone (cleared/logged out), clear local session too
+  //
+  // KEPT (session-sync cutover audit, Task 5): this is NOT redundant with the
+  // `SessionClient` socket (`device:<deviceId>`, `session_state` push). That
+  // socket only fires for revocations that flow through oxy-api's
+  // `DeviceSession` authority (`POST /session/device/signout` and friends). A
+  // sign-out at the CENTRAL IdP itself (`auth.oxy.so`'s own `AuthSession` /
+  // `fedcm_session` — e.g. a direct IdP-side sign-out, or an admin/security
+  // revocation there) does not currently touch `DeviceSession` at all, so no
+  // socket push follows — this iframe poll is the ONLY mechanism that catches
+  // it today. A future phase should move this server-side (IdP deactivation
+  // -> `DeviceSession` update -> broadcast over the same socket), at which
+  // point this client-side poll becomes redundant and can be deleted.
   const lastIdPCheckRef = (0, _react.useRef)(0);
   const pendingIdPCleanupRef = (0, _react.useRef)(null);
 
@@ -1839,35 +1838,40 @@ const OxyProvider = ({
       pendingIdPCleanupRef.current = null;
     };
   }, [user, initialized, clearSessionState, resolvedAuthWebUrl]);
-  const activeSession = activeSessionId ? sessions.find(session => session.sessionId === activeSessionId) : undefined;
-  const currentDeviceId = activeSession?.deviceId ?? null;
-  const userId = user?.id;
-  const refreshSessionsWithUser = (0, _react.useCallback)(() => refreshSessions(userId), [refreshSessions, userId]);
-  const handleSessionRemoved = (0, _react.useCallback)(sessionId => {
-    trackRemovedSession(sessionId);
-  }, [trackRemovedSession]);
-  const handleRemoteSignOut = (0, _react.useCallback)(() => {
-    _bloom.toast.info('You have been signed out remotely.');
-    logout().catch(remoteError => logger('Failed to process remote sign out', remoteError));
-  }, [logger, logout]);
-  (0, _useSessionSocket.useSessionSocket)({
-    userId,
-    activeSessionId,
-    currentDeviceId,
-    refreshSessions: refreshSessionsWithUser,
-    clearSessionState,
-    baseURL: oxyServices.getBaseURL(),
-    getAccessToken: () => oxyServices.getAccessToken(),
-    onRemoteSignOut: handleRemoteSignOut,
-    onSessionRemoved: handleSessionRemoved
-  });
+
+  // Exposed `refreshSessions`: re-bootstraps the server-authoritative device
+  // state (`GET /session/device/state`, the SAME request `SessionClient.start()`
+  // makes) and reprojects it via `syncFromClient` — a manual pull-to-refresh
+  // counterpart to the realtime `device:<deviceId>` socket `client.start()`
+  // already owns (there is no per-domain `useSessionSocket` anymore; a REMOTE
+  // sign-out or account change arrives over that socket and is handled by
+  // `syncFromClient`'s subscription below, including the full-sign-out gap fix
+  // documented above it).
+  const refreshSessionsForContext = (0, _react.useCallback)(async () => {
+    await sessionClient.bootstrap();
+    await syncFromClient();
+  }, [sessionClient, syncFromClient]);
+
+  // Exposed `switchSession`: routes through the server-authoritative
+  // `SessionClient` (Fase 3-B) rather than `useSessionManagement`'s own
+  // `switchSession` (which remains, unchanged, for `useAuthOperations`'
+  // internal same-user duplicate-session dedup — a different, legacy
+  // session-validate concept unrelated to switching the device's ACTIVE
+  // account). Resolves the target account from the current device state,
+  // asks the server to switch, reprojects, and returns the now-active user.
   const switchSessionForContext = (0, _react.useCallback)(async sessionId => {
-    // Propagate the activated user so callers (the device-flow sign-in,
-    // `useSwitchSession`'s cache write, account chooser) receive it. The
-    // underlying session-management `switchSession` already resolves the
-    // `User`; the previous `Promise<void>` wrapper discarded it.
-    return switchSession(sessionId);
-  }, [switchSession]);
+    const targetAccountId = sessionClient.getState()?.accounts.find(account => account.sessionId === sessionId)?.accountId;
+    if (!targetAccountId) {
+      throw new Error(`No device account found for session "${sessionId}"`);
+    }
+    await sessionClient.switchAccount(targetAccountId);
+    await syncFromClient();
+    const activeUser = _authStore.useAuthStore.getState().user;
+    if (!activeUser) {
+      throw new Error('Active account profile could not be resolved after switch');
+    }
+    return activeUser;
+  }, [sessionClient, syncFromClient]);
 
   // Identity management wrappers (delegate to KeyManager)
   const hasIdentity = (0, _react.useCallback)(async () => {
@@ -1924,16 +1928,41 @@ const OxyProvider = ({
     }
   }, [isAuthenticated, initialized, tokenReady, refreshAccounts]);
 
+  // Shared post-switch side effects, run identically regardless of which
+  // `switchToAccount` branch handled the switch below: reload the switchable
+  // account graph (the new active account's relationships differ) and
+  // invalidate every query so all data refetches as the new account.
+  const runPostAccountSwitchSideEffects = (0, _react.useCallback)(async () => {
+    await refreshAccounts();
+    queryClient.invalidateQueries();
+  }, [refreshAccounts, queryClient]);
+
   // Switch the active session INTO an account from the unified graph. In the
-  // REAL-SESSION model this is identical to switching device sign-ins: mint a
-  // real session for the target and make the whole app that account. The removed
-  // `X-Acting-As` delegation header is gone — `oxyServices.switchToAccount`
-  // plants the minted access token (the refresh token is the server-set httpOnly
-  // `oxy_rt_<authuser>` cookie, so the session joins the device multi-account set
-  // and survives reload / `refresh-all`). We then commit the session into context
-  // state the SAME way sign-in / `switchSession` do, refresh the account graph,
-  // and invalidate every query so all data reloads as the new account.
+  // REAL-SESSION model this is identical to switching device sign-ins: the
+  // whole app becomes that account. There is exactly ONE uniform path for
+  // that — the device's server-authoritative `SessionClient.switchAccount()`
+  // — used for EVERY switch, org/managed accounts included:
+  //
+  //  - If `accountId` is ALREADY registered on this device's multi-account
+  //    set (a prior `switchToAccount`/sign-in already added it), switch
+  //    straight through `sessionClient.switchAccount()` — the SAME path
+  //    `switchSession` uses for ordinary device sessions. No new session is
+  //    minted, so no session churn / deactivation of the account's existing
+  //    session (H4).
+  //  - Only the FIRST time an account is switched into does it need minting:
+  //    `oxyServices.switchToAccount` mints+plants a real session, then
+  //    `sessionClient.addCurrentAccount()` registers it into the device set
+  //    (server-set httpOnly `oxy_rt_<authuser>` cookie, so the session joins
+  //    the device multi-account set and survives reload / `refresh-all`).
+  //    Every subsequent switch into that same account takes the branch above.
   const switchToAccount = (0, _react.useCallback)(async accountId => {
+    const deviceState = sessionClient.getState();
+    if (deviceState?.accounts.some(account => account.accountId === accountId)) {
+      await sessionClient.switchAccount(accountId);
+      await syncFromClient();
+      await runPostAccountSwitchSideEffects();
+      return;
+    }
     const result = await oxyServices.switchToAccount(accountId);
     if (!result?.user || !result?.sessionId) {
       throw new Error('Account switch did not return a valid session');
@@ -1945,8 +1974,10 @@ const OxyProvider = ({
 
     // `oxyServices.switchToAccount` already planted `result.accessToken` as the
     // active token; mirror the minted session into the multi-account store and
-    // mark it current, recording the device `authuser` slot so web silent-switch
-    // and the device account chooser can address it.
+    // mark it current. The device account SET (and its `authuser` slot
+    // numbering) is server-authoritative via `SessionClient` — the
+    // `addCurrentAccount` + `syncFromClient` reprojection below supersedes this
+    // local mirror with the server's own state.
     const now = new Date();
     const clientSession = {
       sessionId: result.sessionId,
@@ -1954,20 +1985,35 @@ const OxyProvider = ({
       expiresAt: result.expiresAt || new Date(now.getTime() + DEFAULT_SESSION_VALIDITY_MS).toISOString(),
       lastActive: now.toISOString(),
       userId: result.user.id?.toString() ?? '',
-      isCurrent: true,
-      ...(typeof result.authuser === 'number' ? {
-        authuser: result.authuser
-      } : null)
+      isCurrent: true
     };
     updateSessions([clientSession], {
       merge: true
     });
     setActiveSessionId(result.sessionId);
-    if ((0, _useWebSSO.isWebBrowser)() && typeof result.authuser === 'number') {
-      (0, _activeAuthuser.writeActiveAuthuser)(result.authuser);
-    }
     await persistSessionDurably(result.sessionId);
 
+    // Register the switched-to account into the device's server-authoritative
+    // multi-account set (the SAME `SessionClient.addCurrentAccount()` the
+    // cold-boot handoff uses — it derives identity from the bearer, which
+    // `oxyServices.switchToAccount` already planted above) and reproject
+    // state, so the switch persists across reload / other tabs / devices
+    // instead of only living in this provider's local session-management
+    // state. Best-effort: the token for the new account is already planted, so
+    // a transient failure here must NEVER reject the switch — fall through to
+    // `loginSuccess`/`onAuthStateChange` so the UI reflects the switched-to
+    // account (cold boot re-registers into the device set on next load).
+    // Mirrors the same guard in `handleWebSSOSession`.
+    try {
+      await sessionClient.addCurrentAccount();
+      await syncFromClient();
+    } catch (registrationError) {
+      _core.logger.warn('switchToAccount: failed to register account into device set', {
+        component: 'OxyContext',
+        method: 'switchToAccount'
+      }, registrationError);
+    }
+
     // Fetch the canonical User for the new account (the switch result carries
     // only MinimalUserData); fall back to that minimal shape if the profile
     // fetch fails so the app still reflects the switched identity.
@@ -1985,14 +2031,8 @@ const OxyProvider = ({
     }
     loginSuccess(fullUser);
     onAuthStateChange?.(fullUser);
-
-    // Reload the switchable account graph (the new active account's relationships
-    // differ) and invalidate every query so all data refetches as the new
-    // account — the deviceAccounts probe re-enumerates the multi-account set so
-    // the switched account now appears as a device session.
-    await refreshAccounts();
-    queryClient.invalidateQueries();
-  }, [oxyServices, updateSessions, setActiveSessionId, persistSessionDurably, loginSuccess, onAuthStateChange, refreshAccounts, queryClient]);
+    await runPostAccountSwitchSideEffects();
+  }, [oxyServices, updateSessions, setActiveSessionId, persistSessionDurably, sessionClient, syncFromClient, loginSuccess, onAuthStateChange, runPostAccountSwitchSideEffects]);
   const createAccountFn = (0, _react.useCallback)(async data => {
     const account = await oxyServices.createAccount(data);
     await refreshAccounts();
@@ -2026,7 +2066,7 @@ const OxyProvider = ({
     logoutAll,
     switchSession: switchSessionForContext,
     removeSession: logout,
-    refreshSessions: refreshSessionsWithUser,
+    refreshSessions: refreshSessionsForContext,
     setLanguage,
     getDeviceSessions,
     logoutAllDeviceSessions,
@@ -2043,7 +2083,7 @@ const OxyProvider = ({
     switchToAccount,
     refreshAccounts,
     createAccount: createAccountFn
-  }), [activeSessionId, signIn, signInWithPassword, handleWebSSOSession, currentLanguage, currentLanguageMetadata, currentLanguageName, currentNativeLanguageName, error, getDeviceSessions, hasAccessToken, canUsePrivateApi, isPrivateApiPending, getPublicKey, hasIdentity, isAuthenticated, isLoading, logout, logoutAll, logoutAllDeviceSessions, oxyServices, storageKeyPrefix, clientId, refreshSessionsWithUser, sessions, setLanguage, storage, switchSessionForContext, tokenReady, hasAccessToken, canUsePrivateApi, isPrivateApiPending, authResolved, updateDeviceName, clearAllAccountData, useFollowHook, user, showBottomSheetForContext, openAvatarPicker, accounts, switchToAccount, refreshAccounts, createAccountFn]);
+  }), [activeSessionId, signIn, signInWithPassword, handleWebSSOSession, currentLanguage, currentLanguageMetadata, currentLanguageName, currentNativeLanguageName, error, getDeviceSessions, hasAccessToken, canUsePrivateApi, isPrivateApiPending, getPublicKey, hasIdentity, isAuthenticated, isLoading, logout, logoutAll, logoutAllDeviceSessions, oxyServices, storageKeyPrefix, clientId, refreshSessionsForContext, sessions, setLanguage, storage, switchSessionForContext, tokenReady, hasAccessToken, canUsePrivateApi, isPrivateApiPending, authResolved, updateDeviceName, clearAllAccountData, useFollowHook, user, showBottomSheetForContext, openAvatarPicker, accounts, switchToAccount, refreshAccounts, createAccountFn]);
   return /*#__PURE__*/(0, _jsxRuntime.jsx)(OxyContext.Provider, {
     value: contextValue,
     children: ssoCallbackIntercepting ? null : children