The program had no test that runs it whole. This one starts run() on a nats-server of its own, with the registry container faked on the loopback and node_haves and manifest-reads answered on their call subjects: an away node holds both windows open, its return closes them, each closing said once on distribution.events, a direct write is then refused, reads stay open, the health check answers through the program's port, and a waiter on published wakes on none of the windows' events. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig
distribution
The distribution module of the mesh catalogue: runs the container image registry; claims the seat mesh-artifact-store.
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).