jschoubben
f7e59b876d
The checker's fetch pins only the zero-version requirements a directory's go.mod names (mesh-build-go workspace.go goModOf), so a module reached only through another, such as meshhandacts through meshhandactsclient or mesh-delivery-sdk through meshcatalogclient, was never downloaded and the shut-off load failed (fetch.go:267). The join's merges had dropped these indirect requirements that the trunk's go.mod files list. Builds: design 47 G (join 11, the check's fetch of the group's modules) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
distribution
The distribution module of the mesh catalogue: runs the container image registry; holds the seats container-image-registry
and oci-artifact-registry, and mesh-artifact-store until its window closes. It provides no provision: the store's address
is its listen registry, open to the mesh, which every node-engine finds through the seat's holder (novox/hq ADR 0632). Its
seats' list answers what the store holds, read from the store's own files through its container mesh-registry.
Files it does not know
Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).
/var/lib/mesh/registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2)./var/lib/mesh-registry: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).