Bring the self-hosting guides in line with the shipped code

- geolite2: quote the real commented compose mount (./geolite2 to
  /opt/geolite2, the GEOLITE2_DIR default, so no env var is needed for
  the default path)
- getting-started: healthcheck probes /api/health, not /api/version;
  the environment module reaches archive-api and geocoding-api
  .open-meteo.com, relevant for egress allowlists
- mcp: the module is opt-in and off by default, but no longer the only
  such module
- reverse-proxy: the Coach stream is SSE over plain HTTP, not
  WebSockets; note that TRUST_PROXY_HOPS is not on the bundled compose
  whitelist and must be added by hand
- scaling: /api/health healthcheck; worker liveness is in-memory and
  invisible across a web/worker split; pool sizing now goes through
  getConnectionBudget with DB_CONNECTION_LIMIT as the compose knob and
  a 2-connection pg-boss share
- sso: the native SSO handoff shipped, OIDC_ONLY works with app builds
  that carry it
- unraid: geo databases are baked in only when the build had a licence
  key, or mounted; replaceable either way

docs/self-hosting/getting-started.md

@@ -17,7 +17,8 @@ already installed, longer if a TLS-fronted public hostname is in scope
 - **Outbound HTTPS** to `ghcr.io` (image pulls) plus whichever
   integration endpoints you plan to enable (Withings, OpenAI, etc.).
   The opt-in environmental-context module additionally reaches
-  `api.open-meteo.com` for weather and daylight; it stays off until you
+  `archive-api.open-meteo.com` and `geocoding-api.open-meteo.com` for
+  weather and daylight; it stays off until you
   enable it and set a home location, and every outbound call goes
   through the SSRF-guarded egress wrapper.
 - **Optional but recommended:** a reverse proxy that terminates TLS
@@ -191,8 +192,9 @@ NEXT_PUBLIC_DASHBOARD_SNAPSHOT=false pnpm build
   `app_settings.singleton.registrationEnabled`. The admin panel can
   flip it back if a previous owner closed it.
 - **Service unreachable on `localhost:3000`.** Check `docker compose
-ps` — the `app` healthcheck polls `/api/version` every 30 seconds
-  and will mark the container unhealthy if Postgres is still
+ps` — the `app` healthcheck polls `/api/health` every 30 seconds
+  (it returns 503 while the database or worker is down) and will mark
+  the container unhealthy if Postgres is still
   starting. Tail `docker compose logs db` to confirm Postgres came up
   cleanly.
 - **OAuth callbacks loop back to localhost.** Confirm `APP_URL` and