The foundation modules claim a mesh-scoped seat named after their server

postgres claims mesh-store, lavinmq claims mesh-broker, and the controller's seat is
renamed the-controller -> mesh-controller so all three follow one convention. The resolver
refuses a second holder mesh-wide, so an adopted foundation module assigned to a second node
is refused rather than silently raising a second server. Closes hq issue 056 (ADR 0079).

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

modules/lavinmq/module.json

@@ -7,6 +7,12 @@
       "scope": "mesh"
     }
   ],
+  "claims": [
+    {
+      "name": "mesh-broker",
+      "scope": "mesh"
+    }
+  ],
   "capabilities": [
     "container-runtime"
   ],

modules/mesh-controller/module.json

@@ -7,7 +7,7 @@
   ],
   "claims": [
     {
-      "name": "the-controller",
+      "name": "mesh-controller",
       "scope": "mesh"
     }
   ],

modules/postgres/module.json

@@ -7,6 +7,12 @@
       "scope": "mesh"
     }
   ],
+  "claims": [
+    {
+      "name": "mesh-store",
+      "scope": "mesh"
+    }
+  ],
   "capabilities": [
     "container-runtime"
   ],