jschoubben
b4ab61c0aa
The holder counted against 20 GiB while the bus caps incoming at 8 GiB, so the bus refused writes before the holder said refused naming the cap, and the 80 % finding came too late (running review F2). The cap is read from incoming's binding (the object store's fill); IncomingCap, 8 GiB, is said only where none is read, and the manifest's row holds it equal to max-mib. An abandoned transfer was dropped only on the next publish, and the transfers state's own lifetime dropped its key while its parts stayed: transfers keeps for good, and each open transfer has a key in the new state idle with its own time to live, whose end drops it (re-armed for the rest when it took a part since). registry_incoming reports the bound cap. 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).