Session-flag helpers

A lightweight, non-httpOnly signal cookie (SESSION_FLAG) coordinates the client and server. The client (useSessionFlag / useTokenManager) polls its value and re-fetches the session whenever it changes — so a server-side change the browser can't observe (a cart/checkout mutation, or a guest → authenticated transition) still triggers a client re-sync. These helpers stamp a fresh value from wherever the change happens.

All are exported from @woographql/next/server.

import {
  SESSION_FLAG,
  stampSessionFlag,
  stampSessionFlagForRequest,
  stampSessionFlagForAction,
} from '@woographql/next/server';

The flag value is unique per write (${Date.now()}-${random}), so client watchers re-sync on every change.

// In a route handler — usually via withTokenManager, which calls this for you:
import { stampSessionFlagForRequest } from '@woographql/next/server';

export async function POST(request: Request) {
  const response = NextResponse.json({ ok: true });
  stampSessionFlagForRequest(request, response); // mutates the response cookie jar
  return response;
}

// In a login/register/logout Server Action:
import { stampSessionFlagForAction } from '@woographql/next/server';

export async function loginAction(formData: FormData) {
  'use server';
  // …authenticate…
  await stampSessionFlagForAction(); // client re-syncs the now-authenticated session
}

• useTokenManager — useSessionFlag reads this cookie on the client
• withTokenManager — Stamps the flag automatically after a mutation route
• Server Actions — Where stampSessionFlagForAction is wired
• Library API — Overview of the runtime exports