chore: trim verbose comments in next.js upgrade

The force-dynamic export name is self-documenting; the remaining env.ts comment is tightened to the essential WHY (why we don't use next-runtime-env's helper).

Author: waleedlatif1

apps/sim/app/(landing)/privacy/page.tsx

@@ -3,8 +3,6 @@ import Link from 'next/link'
 import { getEnv } from '@/lib/core/config/env'
 import { ExternalRedirect, LegalLayout } from '@/app/(landing)/components'
 
-/** Opt out of static prerendering so `NEXT_PUBLIC_PRIVACY_URL` is read from
- * the live runtime environment (e.g. Docker-injected) rather than baked at build. */
 export const dynamic = 'force-dynamic'
 
 export const metadata: Metadata = {

apps/sim/app/(landing)/terms/page.tsx

@@ -3,8 +3,6 @@ import Link from 'next/link'
 import { getEnv } from '@/lib/core/config/env'
 import { ExternalRedirect, LegalLayout } from '@/app/(landing)/components'
 
-/** Opt out of static prerendering so `NEXT_PUBLIC_TERMS_URL` is read from
- * the live runtime environment (e.g. Docker-injected) rather than baked at build. */
 export const dynamic = 'force-dynamic'
 
 export const metadata: Metadata = {

apps/sim/app/manifest.ts

@@ -1,8 +1,6 @@
 import type { MetadataRoute } from 'next'
 import { getBrandConfig } from '@/ee/whitelabeling'
 
-/** Opt out of static prerendering so `NEXT_PUBLIC_BRAND_*` is read from
- * the live runtime environment (e.g. Docker-injected) rather than baked at build. */
 export const dynamic = 'force-dynamic'
 
 export default function manifest(): MetadataRoute.Manifest {

apps/sim/lib/core/config/env.ts

@@ -2,17 +2,10 @@ import { createEnv } from '@t3-oss/env-nextjs'
 import { z } from 'zod'
 
 /**
- * Universal environment variable getter that works in both client and server contexts.
- * - Client-side: reads from `window.__ENV`, which `<PublicEnvScript>` from
- *   next-runtime-env populates before hydration (declared globally by that
- *   package). Supports Docker runtime injection of `NEXT_PUBLIC_*` vars
- *   without rebuilding.
- * - Server-side: reads `process.env` directly.
- *
- * We deliberately do not import next-runtime-env's `env()` helper. It calls
- * `unstable_noStore()` from `next/cache`, which Next 16.2+ rejects when
- * invoked outside a request scope (e.g. during `next.config.ts` compilation
- * or top-level module evaluation).
+ * Reads NEXT_PUBLIC_* env vars in both client and server contexts.
+ * Client reads `window.__ENV` (populated by `<PublicEnvScript>`); server reads `process.env`.
+ * We do not use next-runtime-env's `env()` helper because it calls `unstable_noStore()`,
+ * which Next 16.2+ rejects outside a request scope.
  */
 const getEnv = (variable: string): string | undefined => {
   if (typeof window === 'undefined') return process.env[variable]