fix(web): await replay [id] params inside Suspense for Next 16 cacheComponents

Public /replay/[id] (outside the (app)/Clerk group) was statically prerendered at
build and failed cacheComponents' 'uncached data outside <Suspense>' check on
`await params`. Wrap the param-awaiting child in <Suspense> (same pattern as the
home-page searchParams fix). Verified with a full local web build.

Author: iamjr15

apps/web/src/app/replay/[id]/page.tsx

@@ -1,4 +1,5 @@
 import type { Metadata } from "next";
+import { Suspense } from "react";
 import { ReplayView } from "@/components/replay/replay-view";
 
 /**
@@ -13,7 +14,19 @@ export const metadata: Metadata = {
   title: "Replay · Cheatcode",
 };
 
-export default async function ReplayPage({ params }: { params: Promise<{ id: string }> }) {
+// `cacheComponents` (Next 16) requires uncached request data — here `await params`
+// on this public route outside the (app)/Clerk group — to resolve inside a
+// <Suspense> boundary, else static prerender fails with "uncached data accessed
+// outside <Suspense>". Matches the home-page searchParams-in-Suspense pattern.
+export default function ReplayPage({ params }: { params: Promise<{ id: string }> }) {
+  return (
+    <Suspense fallback={null}>
+      <ReplayContent params={params} />
+    </Suspense>
+  );
+}
+
+async function ReplayContent({ params }: { params: Promise<{ id: string }> }) {
   const { id } = await params;
   return <ReplayView id={id} />;
 }