jschoubben
6547933b4d
Kind: short package names (builds, sshkeys, forgemsg, backupgood, diskreadings, grantsstate, busgrants) in `packages`, which the indexer's judge refuses by design 32's rule (a Go package is named by its go.mod's module path). This held mesh-delivery-gate, the build modules, mounts and restic. Each key is now the import path the module's code uses, with its series kept; the manifest tests read the new keys, and the host/machine-name word tests in mounts, nfs-server, mesh-build-node and mesh-delivery-gate look past the path's `git.novox.be/novox/` prefix. Quick fix: only the gate's manifest. Thorough fix (chosen): all 15, since the same refusal holds each. Follow-up for the checker: the candidate verdict lets such a name through (J7(3)), so the merge check did not stop it. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5
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).