A module is a package, not a bare manifest

Each module becomes modules/<name>/ holding module.json, with room for
the rest of what a module is — its tools, health checks, provisioning,
lifecycle — which the conversion from hal still has to bring across.
The flat <name>.json was only the resource-declaration half.

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

modules/registry/module.json

@@ -0,0 +1,52 @@
+{
+  "module": "registry",
+  "version": "1",
+  "provides": [
+    {
+      "name": "artifact-store",
+      "scope": "mesh"
+    }
+  ],
+  "claims": [
+    {
+      "name": "the-artifact-store",
+      "scope": "node"
+    }
+  ],
+  "capabilities": [
+    "container-runtime"
+  ],
+  "serves": {
+    "artifact-store": {
+      "port": 5000
+    }
+  },
+  "listens": [
+    {
+      "port": 5000,
+      "protocol": "tcp",
+      "from": "mesh",
+      "why": "every machine pulls images and artifacts from here"
+    }
+  ],
+  "resources": [
+    {
+      "id": "state",
+      "type": "directory",
+      "path": "/var/lib/mesh/registry",
+      "mode": "0700"
+    },
+    {
+      "id": "store",
+      "type": "container",
+      "name": "mesh-registry",
+      "image": "registry@sha256:a3d8aaa63ed8681a604f1dea0aa03f100d5895b6a58ace528858a7b332415373",
+      "ports": [
+        "5000:5000"
+      ],
+      "volumes": [
+        "mesh-registry-data:/var/lib/registry"
+      ]
+    }
+  ]
+}