Review: four manifests said something stale or nothing at all

dnsmasq still required resolver-data, a provision that died with the
mesh-resolver module — assigning it would refuse with "nothing provides
resolver-data". It asks for the node-zones fact now, at the same path its
config already reads, restarting on the fact's own id.

gitea and verdaccio both provide package-registry now — ADR 0075's provision,
which neither declared, so ADR 0014's "consumes from the private registry" had
no provider anywhere in the catalogue. Two providers, mesh-scoped: the resolver
refuses until one is assigned, and choosing is assigning, which is the designed
shape.

audit-logger runs a container and declared no capability, alone among the
containerised modules. A machine without a runtime would have been assigned it
and failed at apply rather than at assignment.

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

modules/audit-logger/module.json

@@ -57,5 +57,8 @@
       },
       "artifact": "runtime"
     }
+  ],
+  "capabilities": [
+    "container-runtime"
   ]
 }

modules/dnsmasq/module.json

@@ -1,9 +1,6 @@
 {
   "module": "dnsmasq",
   "version": "1",
-  "requires": [
-    "resolver-data"
-  ],
   "provides": [
     "wildcard-resolution"
   ],
@@ -56,8 +53,11 @@
       "boot": "enabled",
       "restart-on": [
         "config",
-        "mesh-resolver.nodes"
+        "dnsmasq.fact-node-zones"
       ]
     }
-  ]
+  ],
+  "facts": {
+    "node-zones": "/etc/mesh-resolver/nodes.conf"
+  }
 }

modules/gitea/module.json

@@ -122,5 +122,11 @@
         "runtime-config"
       ]
     }
+  ],
+  "provides": [
+    {
+      "name": "package-registry",
+      "scope": "mesh"
+    }
   ]
 }

modules/verdaccio/module.json

@@ -99,5 +99,11 @@
   },
   "binds": {
     "route": "/var/lib/mesh/verdaccio/route.json"
-  }
+  },
+  "provides": [
+    {
+      "name": "package-registry",
+      "scope": "mesh"
+    }
+  ]
 }