docs: update documentation to OKF v0.1 format

docs/guides/authenticated-shell.md

@@ -106,6 +106,22 @@ error event. The shell retains the last event state until a later connection suc
 1. Click each quick tab and confirm the matching route and active styling.
 2. Open the user menu and click **Logout**.
 3. Confirm navigation to `/login` and that the event stream is closed.
+4. With **two open tabs** of the same browser profile both on authenticated
+   routes, log out in one. Confirm the *other* tab also navigates to `/login`
+   without any user interaction. See
+   [Cross-Tab Authenticated Shell Invalidation](/guides/cross-tab-invalidation.md)
+   for the full tester matrix (peer logout, SSE unauthorized, negative cases).
+
+## Unauthorized SSE response
+
+1. Sign in once and open the authenticated shell.
+2. Trigger an unauthorized response on `/api/v1/events/status` (e.g. by
+   revoking the refresh cookie via an admin tool or by expiring the session
+   server-side).
+3. Confirm the shell clears, the event stream is closed, and the router
+   navigates to `/login`. The same flow in another open tab is propagated
+   via the cross-tab broadcast — see
+   [Cross-Tab Authenticated Shell Invalidation](/guides/cross-tab-invalidation.md).
 
 # See also