3 Commits

Include renames

Author	SHA1	Message	Date
sneak	0a1277029c	Run only script/cibuild in the Gitea workflow (closes #203) ... The workflow's script/docker-smoke step is removed, so the workflow checks out the repo and runs script/cibuild and nothing else, as the canonical REPO_POLICIES.md says. The owner ruled on the issue that make check covers what needs covering. CI no longer starts the image and waits for its healthcheck. script/docker-smoke and make docker-smoke stay, to run by hand, and the script's header comment no longer says the workflow runs it. The dated TODO.md entries that say the workflow runs it are history and stay as written. Model: opus-5-5	2026-10-21 11:08:34 +00:00
clawbot	582ff66ba6	Describe what --health-interval does in docker-smoke on current Docker (closes #132) ... The old comment said the flag stops the image's 30-second interval from delaying the first probe past the wait. From Docker 25 on, the first probe runs 5 seconds after start either way; the flag makes probes after the 10-second start period come every second instead of every 30. Only the comment changes; TODO.md is left alone because the issue limits the change to this script. Model: opus-5-5	2026-09-28 15:48:53 +02:00
clawbot	b7c1226c38	Add a Docker HEALTHCHECK and make docker-smoke (closes #111) ... The runtime stage declares a HEALTHCHECK that probes /.well-known/healthcheck.json with busybox wget. script/docker-smoke (make docker-smoke) builds the image with script/docker, starts it with a random PIXA_SIGNING_KEY, and passes only once Docker reports the container healthy within 30 seconds; the container is removed on exit and its log printed on failure. The Gitea workflow runs it after script/cibuild; it is not part of make check. It waits on Docker's health status instead of polling a published host port because the Gitea job runs in its own container on its own network, where such a port is not reachable at localhost. Model: opus-5-5	2026-09-28 12:06:29 +02:00