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

internal/bundle/foundation-android.lock

@@ -0,0 +1,12 @@
+// foundation-android.lock — deliberately not a bundle.
+//
+// An android host cannot raise a mesh, and this file says so rather than being an empty
+// placeholder waiting to be filled in.
+//
+// The foundation is a container runtime, a store and the control plane (novox/hq
+// 07-the-foundation.md). An android host implements `file`, `directory` and `action` and refuses
+// `package`, `container` and `service` (ADR 0005) — so every step of the bootstrap is a shape it
+// does not have. No amount of filling this in changes that.
+//
+// **A partial host can JOIN a mesh and cannot BE the first node.** That is a real distinction
+// and it belongs here, where somebody looking for the android bundle will find it.