cherry-pick: revalidate-aggregate route → main

src/app/api/internal/revalidate-aggregate/route.ts

@@ -0,0 +1,40 @@
+import { timingSafeEqual } from "node:crypto";
+import { revalidateTag } from "next/cache";
+import { NextResponse } from "next/server";
+
+export const runtime = "nodejs";
+export const dynamic = "force-dynamic";
+
+/**
+ * Worker-driven CDN cache purge for the aggregate bench snapshot.
+ *
+ * The materialize worker POSTs here after successfully writing a fresh
+ * aggregate JSON to the VPS-served static path. This route invalidates
+ * the `bench-aggregate` cache tag so the next site request re-fetches
+ * the aggregate URL, instead of waiting for the ISR revalidate window.
+ *
+ * Auth: bearer token in `Authorization` header, `REVALIDATE_TOKEN` env,
+ * timing-safe compare. Fails closed when the env is missing.
+ */
+export async function POST(req: Request): Promise<NextResponse> {
+  const secret = (process.env.REVALIDATE_TOKEN ?? "").trim();
+  if (!secret) {
+    return NextResponse.json(
+      { error: "no_secret_configured" },
+      { status: 503 },
+    );
+  }
+  const header = (req.headers.get("authorization") ?? "").trim();
+  const expected = `Bearer ${secret}`;
+  const ok =
+    header.length === expected.length &&
+    timingSafeEqual(Buffer.from(header), Buffer.from(expected));
+  if (!ok) {
+    return NextResponse.json({ error: "unauthorized" }, { status: 401 });
+  }
+  // Next 16's revalidateTag takes a required cache-profile argument.
+  // "default" applies the standard purge semantics for the CDN + ISR
+  // cache layers this route is meant to invalidate.
+  revalidateTag("bench-aggregate", "default");
+  return NextResponse.json({ revalidated: true, tag: "bench-aggregate" });
+}