Session 17: Audit response — checkout 401 fix, hero prop 404 fix, Slate parsing fix, ALL tab cascade isolation, cookie/nav/footer/autocomplete polish (1438 tests)

web/src/app/api/hero-prop/route.ts

@@ -1,11 +1,16 @@
 import { NextResponse } from 'next/server';
 
+// Session 17 — Next.js App Router refuses to compile a route that
+// exports BOTH `dynamic = 'force-dynamic'` AND `revalidate`. The two
+// modes are mutually exclusive: force-dynamic skips static
+// generation; revalidate gates ISR. Session 16 shipped both, which
+// silently broke the route at build time (production audit found a
+// hard 404 on /api/hero-prop).
+//
+// We keep `force-dynamic` (we want the random-prop pick to vary per
+// request) and emit the 15-minute cache via the response's
+// Cache-Control header — Coolify's reverse proxy honors it.
 export const dynamic = 'force-dynamic';
-// Cache the response for 15 minutes (server-side) so cold visitors
-// don't trigger a fresh grade on every page load. The cache header
-// is what most CDNs / Coolify reverse proxies honor; Next.js itself
-// already opts into dynamic rendering via `dynamic = 'force-dynamic'`.
-export const revalidate = 900;
 
 const BACKEND_URL = process.env.BACKEND_URL || 'http://localhost:3000';
 const HERO_FETCH_TIMEOUT_MS = 6000;