The first v0.7.0 publish stopped at preflight because GitHub answers a
missing user package with 404 "Package not found." (documentation_url
.../rest/packages/packages#get-a-package-for-a-user), while the check
only accepted "Not Found", a shape the tests had assumed. Accept that
message too, require the packages documentation URL, and pin the real
body in the tests. Other 404 shapes still stop the job, and the registry
must still report the repository unknown.
The repository is public and the image carries its source label, so the
first GITHUB_TOKEN push creates a public package linked to the repo and
no manual bootstrap is needed. Preflight accepts GitHub's own package
Not Found only when the registry also reports the repository unknown (a
package hidden from the token still has one); every other error still
stops the job. Readback refuses a package still missing after upload,
and the anonymous pull proves it is public.
The repository is public, so a private image only made every deployment
host log in to ghcr.io. Publication now requires the existing package to
be public and linked to ajisaacs/OpenNest (private or wrong association
stops before upload and is rechecked after it), and the clean-runner
verification pulls the returned digest without logging in, proving
anonymous pulls work. Docs describe the one-time package setup and drop
the deployment-host login; the server itself stays LAN-only.