Vanity Route 404 Elimination & Prefetch Resilience
Fixed intermittent 404s when opening public vanity rosters and curator profiles by isolating public reads from stale auth cookies, preserving underscores in handles, eliminating link prefetch stampedes, and bypassing RSC payloads in the Service Worker.
•Vanity Routing, Auth Isolation & Underscore Handles
- Shared a single request-scoped Supabase SSR client per request and routed public vanity profile/roster/item reads through a stateless anonymous server client (with error retries) so expired or mid-rotation JWT cookies never poison navigation with cached 404 responses.
- Preserved underscores in sanitizePostgrestIdentifier and escaped SQL LIKE wildcards via escapePostgrestIlikeLiteral alongside bounded profile queries across vanity routes and /api/og/roster.
•Grid Prefetching, Canonical Community Links & Service Worker Bypass
- Added prefetch={false} on dense card grids across Explore, Profile, Personal Rosters, Leaderboards, Community, Spotlight, and Feed views to prevent concurrent RSC prefetch storms.
- Updated Feed, Spotlight, and /api/search links for official community rosters to route directly to /community/[slug], and updated public/sw.js (curatedlists-v0.14.3) to bypass _rsc and Next.js prefetch/action headers without catch-all interception.