Fix updateTag in migrateChatUser by moving cache invalidation to a Server Action

[Copilot]

updateTag (Next.js 16) is only valid inside Server Actions, but migrateChatUser was called from auth.ts's onLinkAccount callback — not a Server Action — causing a runtime error on sign-in.

Changes

chatHistory.ts — migrateChatUser

• Stripped to DB-only: updates userId on all chat rows, nothing more.
• Removed getPagesList import (no longer needed here).

app/actions/clearUserCache.ts (new)

• Server Action that resolves the current user via initContext() and invalidates all their page cache keys via updateTag + Cloudflare cache.

app/clear-cache/page.tsx (new)

• Thin client page (/clear-cache?redirect=<path>) that calls clearUserCacheAction() on mount, then redirects to the original page (redirect is validated to be relative to prevent open redirect).

accountMenu.tsx

• Sign-in callbackURL changed from pathname → /clear-cache?redirect=<pathname>, routing post-OAuth through the cache-clear page before returning the user.
• Both sign-out handlers: window.location.reload() → router.refresh().

// Before
authClient.signIn.social({ provider: "github", callbackURL: pathname });

// After
authClient.signIn.social({
  provider: "github",
  callbackURL: `/clear-cache?redirect=${encodeURIComponent(pathname)}`,
});

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	my-code	22cd93c	Commit Preview URL Branch Preview URL	Apr 03 2026, 02:27 PM