The mesh's own files for a module are placed by the mesh, not the definition (issue 174)

48 definitions stop naming /var/lib/mesh/<module>: the directory says `place: "mesh"`, the two
subdirectories beneath it (gitea's runtime state, anthropic-manager's output) state their path
beneath it, and every credential, binding, merged file and mount names it as ${dir:mesh-state}.
Resolved on the default root, every definition names exactly the paths it named before —
TestPlacedDirectoriesKeepTheirPaths in mesh-controller, run over both checkouts. Needs the
controller that knows the word (mesh-controller, same branch) one release ahead.

modules/plex/module.json

@@ -13,8 +13,8 @@
     "*.download.completed"
   ],
   "own-secrets": {
-    "broker": "/var/lib/mesh/plex/broker",
-    "token": "/var/lib/mesh/plex/token"
+    "broker": "${dir:mesh-state}/broker",
+    "token": "${dir:mesh-state}/token"
   },
   "listens": [
     {
@@ -51,8 +51,8 @@
     {
       "id": "mesh-state",
       "type": "directory",
-      "path": "/var/lib/mesh/plex",
-      "mode": "0700"
+      "mode": "0700",
+      "place": "mesh"
     },
     {
       "id": "config",
@@ -95,8 +95,8 @@
       "name": "mesh-plex",
       "network": "host",
       "volumes": [
-        "/var/lib/mesh/plex/broker:/run/secrets/broker:ro",
-        "/var/lib/mesh/plex/token:/run/secrets/token:ro",
+        "${dir:mesh-state}/broker:/run/secrets/broker:ro",
+        "${dir:mesh-state}/token:/run/secrets/token:ro",
         "/services/plex/config:/var/lib/plex/config:ro"
       ],
       "env": {