bug: Dockerfile HEALTHCHECK calls non-existent `regen health` subcommand — container always unhealthy

[singret]

Bug

The HEALTHCHECK instruction in the root Dockerfile calls /app/regen health, but no health subcommand exists in the CLI. Docker runs it as a shell command which fails immediately:

/bin/sh: [/app/regen,: not found

The container is permanently marked unhealthy from the first health check onward.

Impact

• docker compose ps shows (unhealthy) for the app container — always, on every fresh deploy
• Any orchestrator or uptime monitor watching Docker health will fire false alerts
• Kubernetes liveness probe based on Docker HEALTHCHECK would restart the container in a loop

Steps to reproduce

make start
docker compose ps   # → fluidify-regen: Up (unhealthy)

Fix

Replace the broken CMD with a wget call against /ready:

HEALTHCHECK --interval=30s --timeout=5s --start-period=30s --retries=3 \
    CMD wget -qO- http://localhost:8080/ready | grep -q '"status":"ready"' || exit 1

Environment

• Docker Compose single-node
• Found during production readiness checklist run