The login step reached the registry but was refused:
Error response from daemon: Get "https://git.clortox.com/v2/": unauthorized
The registry is enabled (an unauthenticated /v2/ returns a proper UNAUTHORIZED
registry error) and a personal access token authenticates against it, so the
automatic token is what lacks the scope. Gitea's automatic token starts
read-only, so the workflow now asks for packages:write. The REGISTRY_TOKEN
fallback stays, and is preferred when set.
The first pipeline run failed at the login step with "no registry token
available". `secrets.*` values only exist when named with an expression, so
`${GITHUB_TOKEN}` in the shell was always empty; both candidate tokens are now
mapped into the step's environment and the shell chooses between them.
The rest of the run was healthy: docker was available to the job and the test
stage passed inside it (Ran 276 tests ... OK).
Runs on pushes to master, tag pushes and pull requests:
* the Dockerfile's new `test` stage runs the whole suite, so a failing
test stops the image from being built or pushed at all
* the image builds with plain docker rather than the buildx and login
actions, so a job never has to reach the internet to fetch third-party
actions -- the most common way a self-hosted runner fails
* it pushes to this instance's registry, deriving the host from
github.server_url instead of hardcoding it
Tags published: `latest` and the branch or tag name (only master moves
`latest`), plus an immutable sha-<short> so an image can be traced back to
its commit. Pull requests build but never push, so a fork cannot publish
into the registry.
Two things the gate caught once it ran inside a container:
* the suite reads config.example.json from the repository root, a hidden
dependency that would have failed the first pipeline run
* `[ "$ref_name" = "$DEFAULT_BRANCH" ]` under `set -u` would have aborted
every branch build if that env key were ever renamed; it now has an
inline fallback
`make test-docker` runs the same gate locally, and README.md documents what
the runner needs: docker reachable from the job, and a token allowed to
write packages.
Also untrack .pi/, which holds pi session task output rather than project
files, and ignore it.