#21: deploy by pulling the images CI built, not by rebuilding on the server

The first deployments died building on the target: four images, and the
webmail build alone was enough to sink it on a small arm64 host - the
build step was killed with no BuildKit error, which is what an exhausted
or overloaded machine looks like from the outside.

The images already exist. CI publishes all four to GHCR for amd64 and
arm64 on every merge, and they are the ones the suite ran against, so
rebuilding them on the deploy target is slower, heavier and less
trustworthy than pulling them.

docker-compose.yaml therefore carries no build definitions, and
docker-compose.build.yaml is the overlay that adds them for local
development and for CI - which does have to exercise the branch rather
than the published images. Both paths were run before committing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/DEPLOYMENT.md

@@ -177,6 +177,10 @@ docker compose pull
 docker compose up -d
 ```
 
+Deploys pull the images CI published rather than building on the server;
+`docker-compose.build.yaml` is the overlay local development uses to build from
+source instead.
+
 Migrations run automatically on start, before the services that depend on them.
 To pin a version, set `IMAGE_TAG` to a release version or a `sha-` tag rather
 than `latest`.