Design 47 H: H-A-387, the artifact registry takes a publish whose reservation names no digest yet

This commit is contained in:
2026-11-22 00:11:30 +01:00
parent ad5284889b
commit 40ad6a10bf
@@ -2443,3 +2443,16 @@ Where two preparers disagreed, the chosen one is named.
H-A-350 answered and no build map carries: the tool runner's put answer (mesh/state.put) carries the entry's fill as
`{"revision": n, "fill": {"count", "bytes", "max_bytes"}}`, buscalls.Fill's form, which mesh-sdk's bundle-side prune
helper reads; built by the mesh-tools developer in H2 beside T1, tested in the runtime's state tests. P3, H-A-227.
- **H-A-387 (the artifact registry takes a publish whose reservation names no digest yet, 00:20)** Since H-A-373 the Go
build module publishes an archive with its reserved version during the build step, when the builder's reservation
still holds an empty digest for every artifact (the builder records digests only at the build's end); the
distribution module's holder (the seat oci-artifact-registry) accepts only an equal digest and says "for another
digest" of an empty one, so every archive-only publish since 00:05 was refused (twelve modules on three nodes, nftables
among them). A-490j decided this on 19 Nov for every holder: a publish is taken when the reserved artifact names that
digest or names none yet; commit ac2cd374 kept the strict check in the distribution holder against it. Fix in the
distribution module (mesh-catalog): holder.Reserved.Recorded takes an empty reserved digest as A-490j says, and its
refusal names the case it met ("reserved for digest X, not Y" or "no reservation of version V"), never "another
digest" for none. Test: a publish against a reservation with no digest yet is taken and marked; one against another
digest is refused naming both. The pack is reproducible (the same archive bytes at 0.1.0, 0.1.1 and the refused
publish). Recovery: rerun the build steps once the distribution module runs on novox. A-490j, P-failure-loud,
fix-a-bug-met-twice (the same symptom met 19 Nov).