fix(legal): render /privacy and /terms dynamically so attribution is current

Both pages were statically generated at build time, baking the default
integration enablement — so a source enabled at runtime (e.g. Overture, now
live on staging) was used but never credited in the data-source/attribution
tables. Mark them force-dynamic like /licenses already is, so they render
per-request against the live API and reflect the integrations actually enabled.

Author: Medformatik

apps/web/src/app/(legal)/privacy/page.tsx

@@ -9,6 +9,12 @@ import { getLocale, getTranslations } from "next-intl/server";
 import { LegalPageShell } from "@/components/legal/LegalPageShell";
 import { privacyNav } from "./sections";
 
+// Render per-request against the live API so the data-source / attribution
+// tables reflect the integrations actually enabled at runtime (matching
+// /licenses). Without this the page is statically built with the default
+// enablement and never credits a runtime-enabled source like Overture.
+export const dynamic = "force-dynamic";
+
 export async function generateMetadata(): Promise<Metadata> {
   const t = await getTranslations("legal");
   return {

apps/web/src/app/(legal)/terms/page.tsx

@@ -8,6 +8,11 @@ import type { Metadata } from "next";
 import { getLocale, getTranslations } from "next-intl/server";
 import { LegalPageShell, type LegalSection } from "@/components/legal/LegalPageShell";
 
+// Render per-request so the data-source / attribution tables reflect the
+// integrations enabled at runtime (matching /licenses), not the build-time
+// default enablement.
+export const dynamic = "force-dynamic";
+
 const sectionsEn: LegalSection[] = [
   { id: sectionSlug("1. Scope and Provider"), label: "Scope and Provider" },
   { id: sectionSlug("2. Description of the Service"), label: "Service Description" },