A definition names no host path for its own data

Twenty-eight modules' data directories are placed: the root as place ".", a sub-directory named by
its id, and every host-side reference — binds, secrets, own secrets, grants, receives, file paths,
mounts, env-files — as ${dir:<id>}. Resolved on the default root every path is the one the manifest
named before, which the controller's TestPlacedDirectoriesKeepTheirPaths proves over both checkouts;
so no data moves and no machine sees a change. Five directories whose id is not their last segment
keep their path as a placement (novox/hq issue 119, ADR 0112, design 27).

modules/records/module.json

@@ -34,8 +34,8 @@
     {
       "id": "checkout",
       "type": "directory",
-      "path": "/var/lib/records",
-      "mode": "0700"
+      "mode": "0700",
+      "place": "."
     },
     {
       "id": "config",
@@ -61,13 +61,13 @@
         "/var/lib/mesh/records/broker:/run/secrets/broker:ro",
         "/var/lib/mesh/records/config.json:/run/config/config.json:ro",
         "/var/lib/mesh/records/origin:/run/config/origin:ro",
-        "/var/lib/records:/var/lib/records"
+        "${dir:checkout}:${dir:checkout}"
       ],
       "env": {
         "MESH_BROKER_FILE": "/run/secrets/broker",
         "MESH_RECORDS_CONFIG_FILE": "/run/config/config.json",
         "MESH_RECORDS_ORIGIN_FILE": "/run/config/origin",
-        "MESH_RECORDS_DIR": "/var/lib/records"
+        "MESH_RECORDS_DIR": "${dir:checkout}"
       },
       "artifact": "runtime",
       "restart-on": [