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/local-model-bed.yml

@@ -11,9 +11,9 @@
 #   openai.env carries OPENAI_BASE_URL=http://<at>:<port>/v1. The test asserts that URL and that a
 #   request to it reaches the running model server.
 #
-#   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
 #   Both modules are pure declaration (a server container + a templated file) — no module runtime image
-#   is built; the bed only stocks the substrate and the ollama server image.
+#   is built; the bed only stocks the foundation and the ollama server image.
 scenario: local-model-bed
 
 segments:
@@ -31,7 +31,7 @@ machines:
     disk: 40GiB
 
 images:
-  - mesh-control:development
+  - mesh-controller:development
 
 place:
   all: [host, runtime]