Answer A-490: a package holder takes the no-parts publish as tag-or-refuse and never reads the artifact store

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-19 16:44:24 +01:00
parent 9ad9511791
commit 325bf58483
@@ -2048,3 +2048,10 @@ the principle that settles it, cited as "design 47 G A-n".
conformance kit has a case that refuses a puller which does not read the runs that started from its module's own
`steps` state, every build module's test runs it, and the catalog's failure-kit check refuses a build module whose
tests do not. (From review round 3 of the build-node step-ends fix.)
- **A-490** (A-73, A-417; principle 7) A package holder (`go-package-registry`, `npm-package-registry`) takes the
no-parts publish as tag-or-refuse: when the forge holds the package's name at the version with that digest it answers
published and moves nothing, else it refuses `not stored`, naming the digest. It never reads the artifact store: a
package's bytes reach the registry only through the build module's one-part publish while it builds, and no copy of
a package is kept anywhere else. A package whose build's publish was refused is built again
(`builder_build_again`), never published from a copy. (Live 2026-11-19: the sdk's build publish refused at 12:25 by
the retired `callers` read; the builder's no-parts republish refused for the parts form.)