@the-portland-company/shell 0.36.1 → 0.36.2

package/dist/app-chrome.cjs

@@ -2770,17 +2770,31 @@ function FrameBody({
     signingOutRef.current = true;
     broadcastLogout();
     signOutRef.current();
+    window.setTimeout(() => {
+      window.location.replace(window.location.href);
+    }, 2e3);
   }, []);
   react.useEffect(
     () => (
-      // A tab that learns of a sign-out elsewhere ends its OWN session properly
-      // (clear cookie, RP-initiated logout at the IdP) rather than merely
-      // navigating away — otherwise its session cookie would outlive the
-      // sign-out and a later visit would silently resume it. No re-broadcast:
-      // the signal that woke us is already on record for everyone.
+      // A tab that learns of a sign-out elsewhere forces a real NAVIGATION
+      // rather than calling the app's own sign-out handler.
+      //
+      // Measured against production before this landed: calling the app's
+      // handler did nothing at all. Apps wire it as
+      // `onSignOut={() => { void signOutAction(); }}` — a server action invoked
+      // outside a transition, so the `redirect()` inside it can never be
+      // applied by the client and the tab just sits there. Building cross-tab
+      // logout on that path made the whole feature a no-op.
+      //
+      // A hard navigation cannot fail that way, and it hands the decision to
+      // the authority rather than guessing: the app's middleware sees a session
+      // whose auth_time predates `politogy_logout_at`, treats it as revoked,
+      // and redirects to Politogy ID. Server-side truth decides; the client
+      // only forces the request. No re-broadcast — the signal that woke us is
+      // already on record for every tab.
       watchLogout(() => {
         if (signingOutRef.current) return;
-        signOutRef.current();
+        window.location.replace(window.location.href);
       })
     ),
     []