Drop host port bindings and the ./api/.env file dependency (not present
in the repo) in favor of Coolify-managed environment variables and its
SERVICE_FQDN_*/SERVICE_URL_* magic vars for auto-generated domains.
Pass the web app's Firebase/API config as Docker build args since the
Nuxt app is generated statically and bakes process.env at build time.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L5D2TYHpgXXXCrUJpcQYxg

pnpm now refuses native postinstall/build scripts for these deps by
default (ERR_PNPM_IGNORED_BUILDS), breaking a plain `pnpm install` in
CI/Docker where there's no TTY to run `pnpm approve-builds`.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L5D2TYHpgXXXCrUJpcQYxg

pnpm's ignored-builds gate (ERR_PNPM_IGNORED_BUILDS) needs the
allowBuilds list from pnpm-workspace.yaml, but the Dockerfile only
copied package.json/pnpm-lock.yaml before running `pnpm install`, so
the allowlist wasn't visible yet and the build failed. Revert the
unrelated package.json "pnpm" field added in 6a1775a since it wasn't
the actual fix.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L5D2TYHpgXXXCrUJpcQYxg

The floating "alpine" tag now resolves to Postgres 18, whose image
refuses to start when the data volume is mounted directly at
/var/lib/postgresql/data (its new expected layout mounts the parent
/var/lib/postgresql instead) -- it errors out even against an empty
volume. Pin to a stable major version compatible with the classic
mount path used here.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L5D2TYHpgXXXCrUJpcQYxg

The api container was crash-looping: logDriver() only uses the plain
console logger when ENV=local, otherwise it unconditionally requires
an Axiom token and log.Fatal()s without one. This deployment has no
Axiom account configured, matching api/.env.docker's own default of
ENV=local for self-hosted setups.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L5D2TYHpgXXXCrUJpcQYxg

…AGGER_HOST

Coolify only writes the port-less SERVICE_URL_<SERVICE> and
SERVICE_FQDN_<SERVICE> into the generated .env used for docker-compose
variable interpolation; the port-suffixed names (SERVICE_URL_WEB_3000,
SERVICE_URL_API_8000, SERVICE_FQDN_API_8000) only exist as
Coolify-injected literals inside each container's own runtime env block,
not as compose-level interpolation sources. Referencing the suffixed
names in `environment:`/`args:` values resolved to empty strings, so
APP_URL and API_BASE_URL were blank — and since the web app is built
statically (nuxt generate, ssr: false), that blank got baked into the
build as the `http://localhost:8000` fallback, breaking the deployed
site for every visitor.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q6NkJzg4XWGQPE5AEeJ6U6

…efault

Self-hosted deployments had no way to disable the per-plan message
send/receive quota (200/month on the free plan) and the "Upgrade to
send more messages" 402 response, unlike the existing
ENTITLEMENT_ENABLED-gated contact/API-key/schedule limits. Add the
same enabled-flag pattern to BillingService so self-hosters aren't
capped by default.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0147RMBR3grGHNtHNj5PypNU