Rename mesh-control -> mesh-controller, substrate -> foundation

One name per thing, per the HQ glossary: the module/container/image/binary/repo
becomes mesh-controller, the seat the-controller, and the store+broker pair the
foundation (embedded base bundles, default template and example lock renamed with
their go:embed directives). No behaviour change — a pure vocabulary rename.

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

scenarios/catalogue-media.yml

@@ -16,7 +16,7 @@
 # after enrol and before the push. Each module additionally OWNS its own config directory
 # (/services/{sonarr,radarr}/config), which the mesh does create.
 #
-#   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/substrate-first-node.lock
+#   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/foundation-first-node.lock
 #   scripts/build-module-runtime.sh {sonarr,radarr} build the two runtime images into the local daemon
 #   (they speak HTTP and need no CLI added). The service images lscr.io/linuxserver/{sonarr,radarr}
 #   must be in the local daemon to be stocked.
@@ -32,14 +32,14 @@ machines:
     at: { segment: hosting, address: [192.0.2.10] }
     egress: true
     inbound: allow
-    # Two *arr apps (server + runtime each) on top of the first-node substrate — seven containers.
+    # Two *arr apps (server + runtime each) on top of the first-node foundation — seven containers.
     # The Servarr images are lighter than catalogue-apps' JVM pair, so catalogue-small's 6GiB is
     # ample headroom.
     memory: 6GiB
     cpus: 4
 
 images:
-  - mesh-control:development
+  - mesh-controller:development
   # The two runtimes built by scripts/build-module-runtime.sh and stocked here.
   - mesh-runtime-sonarr:development
   - mesh-runtime-radarr:development