jschoubben
39cd545814
A read naming no node (an empty node_haves) closed both windows for good (security review F3, second of a kind): the window embeds delivery.WindowHeld and steps by the shared rule, named being every node the read named, and keeps its own guard that a window once closed stays closed. A node-engine whose manifest-reads did not answer (a timeout included) counts as stating nothing as before, and the window's record now says so per node (Why), so registry_old_name tells a timeout from an old node-engine. A read that fails otherwise is an error the wake judges nothing on, no longer taken as not served. 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).