@payez/next-mvp 4.5.5 → 4.5.6

package/dist/api-handlers/session/refresh-viability.d.ts

@@ -2,7 +2,8 @@ import { NextRequest, NextResponse } from 'next/server';
 export declare function GET(req: NextRequest): Promise<NextResponse<{
     canRefresh: boolean;
     reason: string;
-    sessionTokenId: null;
+    error: string;
+    code: string;
 }> | NextResponse<{
     canRefresh: boolean;
     reason: string;
@@ -10,7 +11,5 @@ export declare function GET(req: NextRequest): Promise<NextResponse<{
 }> | NextResponse<{
     canRefresh: boolean;
     reason: string;
-    error: string;
-    code: string;
-    correlationId: string;
+    sessionTokenId: null;
 }>>;

package/dist/api-handlers/session/refresh-viability.js

@@ -7,11 +7,29 @@ const refresh_token_validator_1 = require("../../lib/refresh-token-validator");
 const test_aware_get_token_1 = require("../../lib/test-aware-get-token");
 const logger_1 = require("../../config/logger");
 const token_log_id_1 = require("../../lib/token-log-id");
+const auth_1 = require("../../server/auth");
 async function GET(req) {
     try {
         const sessionToken = req.nextUrl.searchParams.get('token');
         let finalSessionToken = sessionToken;
-        if (!finalSessionToken) {
+        if (!finalSessionToken && process.env.TEST_MODE !== 'true') {
+            // PAY-2216: outside TEST_MODE getTokenTestAware is getSession(), which answered null for a store outage AND
+            // for a deleted session, so this route said not_logged_in to both and its own session_not_found arm (below)
+            // was unreachable from a cookie. Ask for the state instead. Same rules as routes/auth/viability.ts:
+            // 'unknown' never reads as logged out or stale; 'missing' requires a verified cookie.
+            const sessionState = await (0, auth_1.resolveSessionState)(req);
+            if (sessionState.state === 'unknown') {
+                logger_1.logger.warn('[REFRESH-VIABILITY] Session store unavailable - session state unknown');
+                return server_1.NextResponse.json({ canRefresh: false, reason: 'store_unavailable', error: 'Session store unavailable', code: 'STORE_UNAVAILABLE' }, { status: 500 });
+            }
+            if (sessionState.state === 'missing') {
+                return server_1.NextResponse.json({ canRefresh: false, reason: 'session_not_found', sessionTokenId: (0, token_log_id_1.tokenLogId)(sessionState.sessionToken) }, { status: 200 });
+            }
+            if (sessionState.state === 'live') {
+                finalSessionToken = sessionState.session?.session?.token ?? null;
+            }
+        }
+        else if (!finalSessionToken) {
             const token = await (0, test_aware_get_token_1.getTokenTestAware)(req);
             // Support both field names: sessionToken (auth.ts JWT) and redisSessionId (legacy)
             finalSessionToken = (token?.sessionToken || token?.redisSessionId);

package/dist/api-handlers/session/viability.js

@@ -39,8 +39,22 @@ async function GET(req) {
                 code: 'AUTH_NOT_INITIALIZED'
             }, { status: 503 });
         }
-        // Get session from Better Auth
-        const betterAuthSession = await (0, auth_1.getSession)(req);
+        // PAY-2216: the TWIN of routes/auth/viability.ts - same tri-state, same answers, or an app mounting this export
+        // keeps the defect. 'unknown' (store did not answer) is a 5xx and never stale; 'missing' (verified cookie, store
+        // answered "not here") is the stale shape with a token id; 'none' stays { authenticated: false }.
+        const sessionState = await (0, auth_1.resolveSessionState)(req);
+        if (sessionState.state === 'unknown') {
+            console.warn('[VIABILITY] Session store unavailable - session state unknown');
+            return server_1.NextResponse.json({ authenticated: false, revocationStatus: 'unknown', error: 'Session store unavailable', code: 'STORE_UNAVAILABLE' }, { status: 500 });
+        }
+        if (sessionState.state === 'missing') {
+            console.warn('[VIABILITY] Stale cookie detected - verified cookie, session not in Redis');
+            return server_1.NextResponse.json({
+                authenticated: false,
+                sessionTokenId: (0, token_log_id_1.tokenLogId)(sessionState.sessionToken) // PAY-1481: correlation id, never the token
+            });
+        }
+        const betterAuthSession = sessionState.state === 'live' ? sessionState.session : null;
         // Debug logging
         if (!betterAuthSession) {
             console.warn('[VIABILITY] getSession returned null');

package/dist/routes/auth/viability.d.ts

@@ -24,6 +24,13 @@ import { type RevocationStatus } from '../../vibe/sessions';
  * - expiresIn: number - Seconds until token expires
  */
 export declare function GET(req: NextRequest): Promise<NextResponse<{
+    viable: boolean;
+    needsRefresh: boolean;
+    authenticated: boolean;
+    revocationStatus: RevocationStatus;
+    error: string;
+    code: string;
+}> | NextResponse<{
     viable: boolean;
     needsRefresh: boolean;
     authenticated: boolean;
@@ -49,12 +56,4 @@ export declare function GET(req: NextRequest): Promise<NextResponse<{
     expiresAt: string;
     roles: string[];
     clientId: string | null;
-}> | NextResponse<{
-    viable: boolean;
-    needsRefresh: boolean;
-    authenticated: boolean;
-    revocationStatus: RevocationStatus;
-    error: string;
-    code: string;
-    correlationId: string;
 }>>;

package/dist/routes/auth/viability.js

@@ -136,8 +136,37 @@ function resolveClientId(sessionClientId) {
  */
 async function GET(req) {
     try {
-        const baSession = await (0, auth_1.getSession)(req);
-        if (!baSession) {
+        // PAY-2216: ask for the session's STATE, not a session-or-null. A null used to cover a store outage, a deleted
+        // session and no cookie alike, so this route answered 'No session found' to all three and the middleware could
+        // never clear a dead cookie (it must not clear on an outage). See SessionState in server/auth.
+        const sessionState = await (0, auth_1.resolveSessionState)(req);
+        if (sessionState.state === 'unknown') {
+            // The store did not answer. NOT a statement about the session: never stale, never 'No session found'.
+            // Same shape as this route's catch (PAY-1882 step 4): 'unknown' revocation -> the middleware's fail-closed
+            // path, a non-OK answer -> service_error, which never clears cookies.
+            console.warn('[VIABILITY] Session store unavailable - session state unknown');
+            return server_1.NextResponse.json({
+                viable: false,
+                needsRefresh: false,
+                authenticated: false,
+                revocationStatus: 'unknown',
+                error: 'Session store unavailable',
+                code: 'STORE_UNAVAILABLE'
+            }, { status: 500 });
+        }
+        if (sessionState.state === 'missing') {
+            // A VERIFIED cookie and a store that answered "not here". The existing stale shape, so the middleware's
+            // stale_session arm (PAY-2216 / 4.5.4) clears it.
+            console.warn('[VIABILITY] Stale cookie detected - verified cookie, session not in Redis');
+            return server_1.NextResponse.json({
+                viable: false,
+                needsRefresh: false,
+                authenticated: false,
+                sessionTokenId: (0, token_log_id_1.tokenLogId)(sessionState.sessionToken), // PAY-1481: a correlation id, never the token
+                reason: 'Stale session - cookie exists but session not found in Redis'
+            });
+        }
+        if (sessionState.state === 'none') {
             return server_1.NextResponse.json({
                 viable: false,
                 needsRefresh: false,
@@ -145,6 +174,7 @@ async function GET(req) {
                 reason: 'No session found'
             });
         }
+        const baSession = sessionState.session;
         const token = baSession;
         const sessionToken = baSession.session?.token;
         // Try the canonical session-store first; fall back to the Better-Auth-keyed

package/dist/server/auth.d.ts

@@ -78,8 +78,46 @@ export declare function getAuthInstance(): Promise<any>;
  *   getFreshIdpToken              → NO_SESSION (Better Auth cache miss)
  *
  * Returns the session object or null if not authenticated per Redis.
+ *
+ * PAY-2216: this is now a thin wrapper over {@link resolveSessionState} and returns the session ONLY for `live`.
+ * Its signature and every answer it gives are unchanged; callers that must tell a dead session from an
+ * unreachable store call resolveSessionState directly.
  */
 export declare function getSession(request?: Request): Promise<any>;
+/**
+ * PAY-2216: what the session store said about this request's cookie. `getSession()` collapses all three
+ * non-live answers to `null`, and that collapse is the defect this type exists to undo.
+ *
+ * MEASURED (PAY-2216, NextPert 2026-10-11, portal fe547fa4 / next-mvp 4.5.4 / ioredis 5.3.2, real server):
+ * a Redis OUTAGE and a really DELETED key both came out of getSession() as `null`, so viability answered the
+ * identical `200 No session found` for both. Clearing on that shape would log every live user out on an
+ * outage (the PAY-2147 class), so nothing cleared at all and a dead cookie lingered.
+ *
+ *   live    - the session resolved. `session` is exactly what getSession() returns.
+ *   missing - a cookie whose signature VERIFIED (HMAC or JWS, resolveVerifiedSessionTokenFromRequest) and BOTH
+ *             store reads (canonical `{slug}:sess:{t}` and Better Auth's `ba:{slug}:{t}`) COMPLETED and found
+ *             nothing. The store answered; the session is gone. Clearing the cookie is correct. This includes
+ *             a Redis that restarted EMPTY: those sessions really are gone (BAPert 72093, gate row 6).
+ *   unknown - a store read THREW (connection refused, commandTimeout, max retries). The store did not answer,
+ *             so nothing is known about the session. NEVER clear on this. Callers answer 5xx.
+ *   none    - no session cookie, or a cookie whose signature does not verify, with the store not failing.
+ *             Nothing to clear on our authority: a forged cookie never yields `missing`.
+ *
+ * The rule the whole type exists for: `missing` REQUIRES a verified cookie AND reads that completed. Weaken
+ * either and an outage or a forged cookie becomes a clear.
+ */
+export type SessionState = {
+    state: 'live';
+    session: any;
+} | {
+    state: 'missing';
+    sessionToken: string;
+} | {
+    state: 'unknown';
+} | {
+    state: 'none';
+};
+export declare function resolveSessionState(request?: Request): Promise<SessionState>;
 /**
  * Get normalized session data for the current request.
  *

package/dist/server/auth.js

@@ -41,6 +41,7 @@ var __importStar = (this && this.__importStar) || (function () {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.getAuthInstance = getAuthInstance;
 exports.getSession = getSession;
+exports.resolveSessionState = resolveSessionState;
 exports.getSessionData = getSessionData;
 exports.getIdpToken = getIdpToken;
 exports.getFreshIdpToken = getFreshIdpToken;
@@ -230,18 +231,32 @@ function logNoSessionWithKeys(origin, sessionToken) {
  *   getFreshIdpToken              → NO_SESSION (Better Auth cache miss)
  *
  * Returns the session object or null if not authenticated per Redis.
+ *
+ * PAY-2216: this is now a thin wrapper over {@link resolveSessionState} and returns the session ONLY for `live`.
+ * Its signature and every answer it gives are unchanged; callers that must tell a dead session from an
+ * unreachable store call resolveSessionState directly.
  */
 async function getSession(request) {
+    const state = await resolveSessionState(request);
+    return state.state === 'live' ? state.session : null;
+}
+async function resolveSessionState(request) {
     const auth = await getAuthInstance();
     if (!request)
-        return null;
+        return { state: 'none' };
     // Path A — Better Auth primary path (cookie cache → secondary storage).
     // Fast happy-path when both Better Auth and Redis agree.
+    //
+    // PAY-2216: secondaryStorage.get RETHROWS a Redis failure on purpose (170033), so a throw here means "the store
+    // could not be asked". It is remembered: if Path B then has no verified token to read with, the honest answer is
+    // `unknown`, not `none`.
     let betterAuthSession = null;
+    let primaryThrew = false;
     try {
         betterAuthSession = await auth.api.getSession({ headers: request.headers });
     }
     catch (err) {
+        primaryThrew = true;
         logSessionReadSwallowed('primary', err); // fall through to canonical Redis path
     }
     if (betterAuthSession?.session?.token && betterAuthSession?.user) {
@@ -257,7 +272,7 @@ async function getSession(request) {
         }
         if (!sessionData)
             sessionData = buildSessionDataFromAuthSession(betterAuthSession);
-        return attachSessionData(betterAuthSession, sessionData, sessionToken);
+        return { state: 'live', session: attachSessionData(betterAuthSession, sessionData, sessionToken) };
     }
     // Path B — Better Auth said null/incomplete. Fall back to a VERIFIED cookie
     // decode + Redis-canonical liveness check. This catches cases where the
@@ -271,8 +286,12 @@ async function getSession(request) {
     // the signature position, and a forged JWS too. The token now comes only from
     // the shared verified resolver (HMAC or JWS signature checked first).
     const sessionToken = await (0, verified_session_token_1.resolveVerifiedSessionTokenFromRequest)(request);
+    // No verified token. If Better Auth's read THREW, the store was failing, so we cannot say the cookie is
+    // unverifiable rather than unreadable: `unknown`. Otherwise there is nothing to act on: `none`.
     if (!sessionToken)
-        return null;
+        return primaryThrew ? { state: 'unknown' } : { state: 'none' };
+    // PAY-2216: both reads must COMPLETE for a miss to mean anything. Either one throwing is `unknown`, which
+    // nobody may clear on. These two functions do a bare redis.get and do not swallow (verified at 4.5.4).
     let sessionData = null;
     try {
         sessionData = await (0, session_store_1.getSession)(sessionToken);
@@ -281,9 +300,10 @@ async function getSession(request) {
     }
     catch (err) {
         logSessionReadSwallowed('B', err); // Redis unavailable
+        return { state: 'unknown' };
     }
     if (!sessionData)
-        return null;
+        return { state: 'missing', sessionToken };
     // Synthesize a minimal session shape compatible with downstream callers.
     // The `session.token` field is what `getFreshIdpToken` and other callers
     // read to drive `ensureFreshAccessToken` + Redis lookups, so it MUST be
@@ -296,7 +316,7 @@ async function getSession(request) {
             roles: sessionData.roles,
         },
     };
-    return attachSessionData(synthetic, sessionData, sessionToken);
+    return { state: 'live', session: attachSessionData(synthetic, sessionData, sessionToken) };
 }
 /**
  * Get normalized session data for the current request.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@payez/next-mvp",
-  "version": "4.5.5",
+  "version": "4.5.6",
   "sideEffects": false,
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/src/api-handlers/session/refresh-viability.ts

@@ -4,12 +4,29 @@ import { checkRefreshViability } from '../../lib/refresh-token-validator';
 import { getTokenTestAware } from '../../lib/test-aware-get-token';
 import { logger } from '../../config/logger';
 import { tokenLogId } from '../../lib/token-log-id';
+import { resolveSessionState } from '../../server/auth';
 
 export async function GET(req: NextRequest) {
   try {
     const sessionToken = req.nextUrl.searchParams.get('token');
     let finalSessionToken = sessionToken;
-    if (!finalSessionToken) {
+    if (!finalSessionToken && process.env.TEST_MODE !== 'true') {
+      // PAY-2216: outside TEST_MODE getTokenTestAware is getSession(), which answered null for a store outage AND
+      // for a deleted session, so this route said not_logged_in to both and its own session_not_found arm (below)
+      // was unreachable from a cookie. Ask for the state instead. Same rules as routes/auth/viability.ts:
+      // 'unknown' never reads as logged out or stale; 'missing' requires a verified cookie.
+      const sessionState = await resolveSessionState(req);
+      if (sessionState.state === 'unknown') {
+        logger.warn('[REFRESH-VIABILITY] Session store unavailable - session state unknown');
+        return NextResponse.json({ canRefresh: false, reason: 'store_unavailable', error: 'Session store unavailable', code: 'STORE_UNAVAILABLE' }, { status: 500 });
+      }
+      if (sessionState.state === 'missing') {
+        return NextResponse.json({ canRefresh: false, reason: 'session_not_found', sessionTokenId: tokenLogId(sessionState.sessionToken) }, { status: 200 });
+      }
+      if (sessionState.state === 'live') {
+        finalSessionToken = sessionState.session?.session?.token ?? null;
+      }
+    } else if (!finalSessionToken) {
       const token = await getTokenTestAware(req);
       // Support both field names: sessionToken (auth.ts JWT) and redisSessionId (legacy)
       finalSessionToken = (token?.sessionToken || token?.redisSessionId) as string;

package/src/api-handlers/session/viability.ts

@@ -6,7 +6,7 @@
 
 import { NextRequest, NextResponse } from 'next/server';
 import { getSession as getRedisSession, getBetterAuthSession } from '../../lib/session-store';
-import { getSession } from '../../server/auth';
+import { resolveSessionState } from '../../server/auth';
 import { isInitializationFailed, ensureInitialized } from '../../lib/startup-init';
 import { getIDPClientConfig } from '../../lib/idp-client-config';
 import { tokenLogId } from '../../lib/token-log-id';
@@ -45,8 +45,25 @@ export async function GET(req: NextRequest) {
       );
     }
 
-    // Get session from Better Auth
-    const betterAuthSession = await getSession(req);
+    // PAY-2216: the TWIN of routes/auth/viability.ts - same tri-state, same answers, or an app mounting this export
+    // keeps the defect. 'unknown' (store did not answer) is a 5xx and never stale; 'missing' (verified cookie, store
+    // answered "not here") is the stale shape with a token id; 'none' stays { authenticated: false }.
+    const sessionState = await resolveSessionState(req);
+    if (sessionState.state === 'unknown') {
+      console.warn('[VIABILITY] Session store unavailable - session state unknown');
+      return NextResponse.json(
+        { authenticated: false, revocationStatus: 'unknown' as RevocationStatus, error: 'Session store unavailable', code: 'STORE_UNAVAILABLE' },
+        { status: 500 }
+      );
+    }
+    if (sessionState.state === 'missing') {
+      console.warn('[VIABILITY] Stale cookie detected - verified cookie, session not in Redis');
+      return NextResponse.json({
+        authenticated: false,
+        sessionTokenId: tokenLogId(sessionState.sessionToken) // PAY-1481: correlation id, never the token
+      });
+    }
+    const betterAuthSession = sessionState.state === 'live' ? sessionState.session : null;
 
     // Debug logging
     if (!betterAuthSession) {

package/src/routes/auth/viability.ts

@@ -15,7 +15,7 @@
  */
 
 import { NextRequest, NextResponse } from 'next/server';
-import { getSession as getBetterAuthSession } from '../../server/auth';
+import { resolveSessionState } from '../../server/auth';
 import {
   getSession as getRedisSession,
   getBetterAuthSession as getBetterAuthRedisSession,
@@ -142,9 +142,40 @@ function resolveClientId(sessionClientId: string | undefined): string | null {
  */
 export async function GET(req: NextRequest) {
   try {
-    const baSession = await getBetterAuthSession(req);
+    // PAY-2216: ask for the session's STATE, not a session-or-null. A null used to cover a store outage, a deleted
+    // session and no cookie alike, so this route answered 'No session found' to all three and the middleware could
+    // never clear a dead cookie (it must not clear on an outage). See SessionState in server/auth.
+    const sessionState = await resolveSessionState(req);
 
-    if (!baSession) {
+    if (sessionState.state === 'unknown') {
+      // The store did not answer. NOT a statement about the session: never stale, never 'No session found'.
+      // Same shape as this route's catch (PAY-1882 step 4): 'unknown' revocation -> the middleware's fail-closed
+      // path, a non-OK answer -> service_error, which never clears cookies.
+      console.warn('[VIABILITY] Session store unavailable - session state unknown');
+      return NextResponse.json({
+        viable: false,
+        needsRefresh: false,
+        authenticated: false,
+        revocationStatus: 'unknown' as RevocationStatus,
+        error: 'Session store unavailable',
+        code: 'STORE_UNAVAILABLE'
+      }, { status: 500 });
+    }
+
+    if (sessionState.state === 'missing') {
+      // A VERIFIED cookie and a store that answered "not here". The existing stale shape, so the middleware's
+      // stale_session arm (PAY-2216 / 4.5.4) clears it.
+      console.warn('[VIABILITY] Stale cookie detected - verified cookie, session not in Redis');
+      return NextResponse.json({
+        viable: false,
+        needsRefresh: false,
+        authenticated: false,
+        sessionTokenId: tokenLogId(sessionState.sessionToken), // PAY-1481: a correlation id, never the token
+        reason: 'Stale session - cookie exists but session not found in Redis'
+      });
+    }
+
+    if (sessionState.state === 'none') {
       return NextResponse.json({
         viable: false,
         needsRefresh: false,
@@ -153,6 +184,8 @@ export async function GET(req: NextRequest) {
       });
     }
 
+    const baSession = sessionState.session;
+
     const token = baSession as any;
     const sessionToken = baSession.session?.token;
 

package/src/server/auth.ts

@@ -221,17 +221,60 @@ function logNoSessionWithKeys(origin: 'b' | 'c', sessionToken: string): void {
  *   getFreshIdpToken              → NO_SESSION (Better Auth cache miss)
  *
  * Returns the session object or null if not authenticated per Redis.
+ *
+ * PAY-2216: this is now a thin wrapper over {@link resolveSessionState} and returns the session ONLY for `live`.
+ * Its signature and every answer it gives are unchanged; callers that must tell a dead session from an
+ * unreachable store call resolveSessionState directly.
  */
 export async function getSession(request?: Request): Promise<any> {
+  const state = await resolveSessionState(request);
+  return state.state === 'live' ? state.session : null;
+}
+
+/**
+ * PAY-2216: what the session store said about this request's cookie. `getSession()` collapses all three
+ * non-live answers to `null`, and that collapse is the defect this type exists to undo.
+ *
+ * MEASURED (PAY-2216, NextPert 2026-10-11, portal fe547fa4 / next-mvp 4.5.4 / ioredis 5.3.2, real server):
+ * a Redis OUTAGE and a really DELETED key both came out of getSession() as `null`, so viability answered the
+ * identical `200 No session found` for both. Clearing on that shape would log every live user out on an
+ * outage (the PAY-2147 class), so nothing cleared at all and a dead cookie lingered.
+ *
+ *   live    - the session resolved. `session` is exactly what getSession() returns.
+ *   missing - a cookie whose signature VERIFIED (HMAC or JWS, resolveVerifiedSessionTokenFromRequest) and BOTH
+ *             store reads (canonical `{slug}:sess:{t}` and Better Auth's `ba:{slug}:{t}`) COMPLETED and found
+ *             nothing. The store answered; the session is gone. Clearing the cookie is correct. This includes
+ *             a Redis that restarted EMPTY: those sessions really are gone (BAPert 72093, gate row 6).
+ *   unknown - a store read THREW (connection refused, commandTimeout, max retries). The store did not answer,
+ *             so nothing is known about the session. NEVER clear on this. Callers answer 5xx.
+ *   none    - no session cookie, or a cookie whose signature does not verify, with the store not failing.
+ *             Nothing to clear on our authority: a forged cookie never yields `missing`.
+ *
+ * The rule the whole type exists for: `missing` REQUIRES a verified cookie AND reads that completed. Weaken
+ * either and an outage or a forged cookie becomes a clear.
+ */
+export type SessionState =
+  | { state: 'live'; session: any }
+  | { state: 'missing'; sessionToken: string }
+  | { state: 'unknown' }
+  | { state: 'none' };
+
+export async function resolveSessionState(request?: Request): Promise<SessionState> {
   const auth = await getAuthInstance();
-  if (!request) return null;
+  if (!request) return { state: 'none' };
 
   // Path A — Better Auth primary path (cookie cache → secondary storage).
   // Fast happy-path when both Better Auth and Redis agree.
+  //
+  // PAY-2216: secondaryStorage.get RETHROWS a Redis failure on purpose (170033), so a throw here means "the store
+  // could not be asked". It is remembered: if Path B then has no verified token to read with, the honest answer is
+  // `unknown`, not `none`.
   let betterAuthSession: any = null;
+  let primaryThrew = false;
   try {
     betterAuthSession = await auth.api.getSession({ headers: request.headers });
   } catch (err) {
+    primaryThrew = true;
     logSessionReadSwallowed('primary', err); // fall through to canonical Redis path
   }
 
@@ -245,7 +288,7 @@ export async function getSession(request?: Request): Promise<any> {
       logSessionReadSwallowed('A', err); // Redis unavailable
     }
     if (!sessionData) sessionData = buildSessionDataFromAuthSession(betterAuthSession);
-    return attachSessionData(betterAuthSession, sessionData, sessionToken);
+    return { state: 'live', session: attachSessionData(betterAuthSession, sessionData, sessionToken) };
   }
 
   // Path B — Better Auth said null/incomplete. Fall back to a VERIFIED cookie
@@ -260,16 +303,21 @@ export async function getSession(request?: Request): Promise<any> {
   // the signature position, and a forged JWS too. The token now comes only from
   // the shared verified resolver (HMAC or JWS signature checked first).
   const sessionToken = await resolveVerifiedSessionTokenFromRequest(request);
-  if (!sessionToken) return null;
+  // No verified token. If Better Auth's read THREW, the store was failing, so we cannot say the cookie is
+  // unverifiable rather than unreadable: `unknown`. Otherwise there is nothing to act on: `none`.
+  if (!sessionToken) return primaryThrew ? { state: 'unknown' } : { state: 'none' };
 
+  // PAY-2216: both reads must COMPLETE for a miss to mean anything. Either one throwing is `unknown`, which
+  // nobody may clear on. These two functions do a bare redis.get and do not swallow (verified at 4.5.4).
   let sessionData: SessionData | null = null;
   try {
     sessionData = await getRedisSession(sessionToken);
     if (!sessionData) sessionData = await getBetterAuthRedisSession(sessionToken);
   } catch (err) {
     logSessionReadSwallowed('B', err); // Redis unavailable
+    return { state: 'unknown' };
   }
-  if (!sessionData) return null;
+  if (!sessionData) return { state: 'missing', sessionToken };
 
   // Synthesize a minimal session shape compatible with downstream callers.
   // The `session.token` field is what `getFreshIdpToken` and other callers
@@ -283,7 +331,7 @@ export async function getSession(request?: Request): Promise<any> {
       roles: sessionData.roles,
     },
   };
-  return attachSessionData(synthetic, sessionData, sessionToken);
+  return { state: 'live', session: attachSessionData(synthetic, sessionData, sessionToken) };
 }
 
 /**