mesh-cli requires the console's endpoint and writes its address

nox now reaches the mesh through this machine's console, so the module
requires mcp-endpoint and writes the bound address to /etc/mesh-cli/console
rather than trusting a fixed port. No invokes: mesh-cli has no bus account,
and one nothing dials would only be minted.

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

modules/mesh-cli/module.json

@@ -2,6 +2,9 @@
   "module": "mesh-cli",
   "version": "1",
   "moved": true,
+  "requires": [
+    "mcp-endpoint"
+  ],
   "resources": [
     {
       "id": "program",
@@ -9,6 +12,20 @@
       "artifact": "program",
       "path": "/usr/local/bin",
       "unknown": "program"
+    },
+    {
+      "id": "console-dir",
+      "type": "directory",
+      "path": "/etc/mesh-cli",
+      "mode": "0755",
+      "unknown": "program"
+    },
+    {
+      "id": "console",
+      "type": "file",
+      "path": "/etc/mesh-cli/console",
+      "mode": "0644",
+      "template": "files/console"
     }
   ],
   "items": [