Applied the findings that held up against the code:
- strict vMAJOR.MINOR.PATCH guard; v[0-9]* accepted v1, v1-foo and
prereleases, all valid registry tags
- latest now follows the newest release, so replaying an older tag cannot
drag it backwards; skipped with a warning if the tag list is unavailable
- smoke test starts the built image and requires 2xx on / before pushing
- timeout-minutes: 20 on the job, so a hung build cannot hold the
capacity-1 runner indefinitely
- the decision doc records the socket's blast radius: root-equivalent,
runner-wide, only on a label PR jobs cannot use
Rejected with evidence: the .dockerignore leak (.env*, *.pem, .git are
excluded) and the Docker client/daemon API mismatch (20.10.24 client
against a 29.9.2 daemon builds over the socket).
Build Dockerfile on every v* tag push (created by release-please when the
release PR merges) and push registry.noelsabia.dev/cv_website/nuxt as the
version, sha-<12> and latest. Main pushes do not build: the registry holds
releases, not commits.
The job runs in node:22-bookworm and needs only the Docker client, so the
act_runner must expose its host socket (container.docker_host: automount);
a preflight step fails with that cause when it does not.