Production-ready wiring: VAPID prop fix, port mappings, AUTH_URL

- PushOptIn now accepts vapidKey as a prop from its server-component
  parent (settings page reads VAPID_PUBLIC_KEY at runtime) — eliminates
  the NEXT_PUBLIC_* build-time dependency so pre-built GHCR images work
  without a build arg.
- deploy/compose.yaml: famapp exposes 3010:3000, authentik-server exposes
  9200:9000 so the existing Caddy stack can proxy by IP, matching every
  other service in the homelab.  NEXT_PUBLIC_APP_URL replaced by AUTH_URL
  (correct next-auth v5 var).
- deploy/Caddyfile.snippet: updated to 192.168.1.69:3010 / :9200.
- .env.production.example: AUTH_URL, ntfy pre-wired to ntfy.ginnoir.com,
  VAPID_SUBJECT prefilled with real email.
- typecheck and pnpm build both pass.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

src/app/settings/page.tsx

@@ -14,6 +14,7 @@ export default async function SettingsPage() {
   const { user } = await getCurrentSession();
   const shareLinks = await getActiveShareLinks();
   const ntfyConfigured = !!(process.env["NTFY_URL"] && process.env["NTFY_TOPIC"]);
+  const vapidKey = process.env["VAPID_PUBLIC_KEY"] ?? "";
 
   return (
     <div className="container max-w-2xl py-8 space-y-6">
@@ -46,7 +47,7 @@ export default async function SettingsPage() {
           <CardTitle>Push Notifications</CardTitle>
         </CardHeader>
         <CardContent>
-          <PushOptIn />
+          <PushOptIn vapidKey={vapidKey} />
         </CardContent>
       </Card>