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

@@ -0,0 +1,55 @@
+{
+  "module": "grafana",
+  "version": "1",
+  "own-secrets": {
+    "admin": "/var/lib/grafana-module/admin.secret"
+  },
+  "capabilities": [
+    "container-runtime"
+  ],
+  "listens": [
+    {
+      "port": 3000,
+      "protocol": "tcp",
+      "from": "mesh",
+      "why": "the dashboards. Also 3000 inside, like the forge - which is the mesh's port assignment earning its keep"
+    }
+  ],
+  "resources": [
+    {
+      "id": "state",
+      "type": "directory",
+      "path": "/var/lib/grafana-module",
+      "mode": "0700"
+    },
+    {
+      "id": "server-env",
+      "type": "file",
+      "path": "/var/lib/grafana-module/server.env",
+      "mode": "0600",
+      "content": "GF_SECURITY_ADMIN_PASSWORD=${secret:admin}\n"
+    },
+    {
+      "id": "data",
+      "type": "directory",
+      "path": "/services/grafana/data",
+      "mode": "0700",
+      "owner": "472:472"
+    },
+    {
+      "id": "server",
+      "type": "container",
+      "name": "grafana",
+      "image": "grafana/grafana@sha256:f772d434e8fab0049deb2b1b30abd43342bcfca1537614aa8d36080232cf4283",
+      "env-file": [
+        "/var/lib/grafana-module/server.env"
+      ],
+      "ports": [
+        "3000"
+      ],
+      "volumes": [
+        "/services/grafana/data:/var/lib/grafana"
+      ]
+    }
+  ]
+}