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

test/amqp.test.ts

@@ -27,7 +27,7 @@ test("a module's tool serves and is invoked over a real AMQP broker", { skip: !u
   const serverBroker = await connectAmqp(url!);
   const stop = await runTools({ broker: serverBroker, moduleEntrypoints: [] });
 
-  // A separate connection — a caller, like mesh-control's command API — invokes over the broker,
+  // A separate connection — a caller, like mesh-controller's command API — invokes over the broker,
   // by module and tool (novox/hq ADR 0047: served on serve.demo.greet, invoked as demo.greet).
   const caller = await connectAmqp(url!);
   const result = (await invokeTool(caller, "demo", "greet", { who: "mesh" })) as { hello: string };