## Why

The production server only provides Docker and does not have Node.js installed. We need a way to refresh the site to the latest content on that server without installing Node.js on the host.

## What Changes

- Add a Docker-first mechanism to update the deployed site to the latest content without requiring host-installed build tooling (no Node.js on the server).
- Standardize the deploy/update flow so the server updates are performed via Docker (e.g., pulling a new artifact/image and restarting, or running a containerized refresh job).
- Document and automate the update command(s) so content refresh is repeatable and low-risk.

## Capabilities

### New Capabilities
- `docker-content-refresh`: The deployed site can be updated to the latest content on a Docker-only server (no host Node.js), using a containerized workflow.

### Modified Capabilities

None.

## Impact

- Deployment/runtime: Docker compose/service definitions, update procedure, and operational docs.
- CI/CD: build/publish pipeline may need to produce and publish deployable artifacts suitable for Docker-only servers.
- Secrets/credentials: any content source credentials needed for refresh/build must be handled via Docker-friendly secret injection.
- Observability/ops: add or adjust logging/health checks around the refresh/update step to make failures visible.