distribution's program listens on 5100 and the registry container on 5001, so no mapping names the store's port

The composer finds a listen's machine port in a container mapping that names
it on either side (MachineSide). The program's listen 5000 matched the
registry container's inner 5000 in 127.0.0.1:5001:5000, so the store's address
became the container's loopback side and the program's own port was never
opened: the move to 83cd1a3d on 2026-11-08 23:25 UTC cut the artifact store off
(issue 1966 note 109). The program now binds 5100, where every machine fetches
(the artifact-store alias and the seats' reach agree), and the container serves
5001 inside and out. A row holds that no container names 5100.

Undo: revert this commit.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

modules/distribution/module.json

@@ -147,7 +147,7 @@
   "listens": [
     {
       "name": "registry",
-      "port": 5000,
+      "port": 5100,
       "protocol": "tcp",
       "from": "mesh",
       "why": "every machine pulls images and artifacts from here; distribution's program serves it in front of the store"
@@ -195,12 +195,13 @@
       "name": "mesh-registry",
       "image": "registry@sha256:a3d8aaa63ed8681a604f1dea0aa03f100d5895b6a58ace528858a7b332415373",
       "ports": [
-        "127.0.0.1:5001:5000"
+        "127.0.0.1:5001:5001"
       ],
       "volumes": [
         "/var/lib/mesh-registry:/var/lib/registry"
       ],
       "env": {
+        "REGISTRY_HTTP_ADDR": ":5001",
         "REGISTRY_STORAGE_DELETE_ENABLED": "true"
       },
       "health": {
@@ -225,7 +226,7 @@
       "env": {
         "MESH_BROKER_FILE": "/var/lib/mesh/registry/broker",
         "MESH_REGISTRY_LOOPBACK": "http://127.0.0.1:5001",
-        "MESH_REGISTRY_LISTEN": ":5000"
+        "MESH_REGISTRY_LISTEN": ":5100"
       },
       "user": "distribution",
       "health": {