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

@@ -0,0 +1,41 @@
+{
+  "module": "ombi",
+  "version": "1",
+  "capabilities": [
+    "container-runtime"
+  ],
+  "listens": [
+    {
+      "port": 3579,
+      "protocol": "tcp",
+      "from": "mesh",
+      "why": "requests from viewers"
+    }
+  ],
+  "resources": [
+    {
+      "id": "config",
+      "type": "directory",
+      "path": "/services/ombi/config",
+      "mode": "0700",
+      "owner": "1000:1000"
+    },
+    {
+      "id": "server",
+      "type": "container",
+      "name": "ombi",
+      "image": "lscr.io/linuxserver/ombi@sha256:a6f76ac521ba01eee2e9f0c23a3fed22e56630d97a04d5eeaeaa36c1e681640d",
+      "env": {
+        "PUID": "1000",
+        "PGID": "1000",
+        "TZ": "Etc/UTC"
+      },
+      "ports": [
+        "3579"
+      ],
+      "volumes": [
+        "/services/ombi/config:/config"
+      ]
+    }
+  ]
+}