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/portainer/module.json

@@ -0,0 +1,36 @@
+{
+  "module": "portainer",
+  "version": "1",
+  "capabilities": [
+    "container-runtime"
+  ],
+  "listens": [
+    {
+      "port": 9443,
+      "protocol": "tcp",
+      "from": "mesh",
+      "why": "the container dashboard, over its own tls"
+    }
+  ],
+  "resources": [
+    {
+      "id": "data",
+      "type": "directory",
+      "path": "/services/portainer/data",
+      "mode": "0700"
+    },
+    {
+      "id": "server",
+      "type": "container",
+      "name": "portainer",
+      "image": "portainer/portainer-ce@sha256:511f3f06c96fe3b993ebeaafde311c1959cae73a7ef825dba6397d51b450dffa",
+      "ports": [
+        "9443"
+      ],
+      "volumes": [
+        "/services/portainer/data:/data",
+        "/var/run/docker.sock:/var/run/docker.sock"
+      ]
+    }
+  ]
+}