Bundle-release hotfix for the v1.4.34.1 deploy stall. The GHCR image for v1.4.34.1 published successfully, but Coolify's `docker compose up` on the apps-01 host kept reusing the cached `:latest` digest because `docker-compose.yml` had no pull policy declared — Docker's default ("only pull if missing") happily skipped the registry round-trip and restarted the container with the prior v1.4.34 image, completing each deploy in ~20 s without ever fetching the new manifest.
Changed
- `docker-compose.yml` now declares `pull_policy: always` on the `app` service. Compose-up re-checks the registry digest on every `up` and pulls when GHCR has a newer manifest, regardless of the tag string. The minor bandwidth cost per deploy is the price of correctness; the alternative — pinning to a version tag per release — would require every operator (self-host included) to bump the tag on every release. v1.4.34.1's perf work (SQL-side aggregator for `/api/insights/comprehensive`, 5 additional cache wraps, scatter-card sizing) ships through the same `:latest` tag that the new deploy will actually pull.