Establish the repo for the completed Phase 0-3 build

Settles the design repository now that the self-upgrade build is on main:
- Records the two decisions that shipped without a record — ADR 0077 (the
  controller/foundation/node vocabulary) and ADR 0078 (the store and broker are
  ordinary modules); accepts ADR 0075 and 0076, which shipped work rests on.
- Fills issue 051's amended-design and wires ADR 0078 into 07-the-foundation.
- Sweeps the repo rename (mesh-control -> mesh-controller) into the mutable docs
  now that the forge repo is renamed; updates the glossary note and repos.md.
- Fixes the six broken links from the design-doc renames, indexes the glossary,
  regenerates the decisions reading order.

Both checks (records.py, index.py) are green. Statuses stay honest: the build is
on main and lab-proven but not deployed as the production mesh, so the to-be docs
remain in-progress and the as-is layer (the hal mesh) is unchanged — graduation
to implemented + as-is belongs to deployment, not merge.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

00-META/process/06-writing-a-module.md

@@ -58,7 +58,7 @@ Three questions, answered from the machine:
    A **provisioner** is the exception: it reads a password file, so it mounts the `.secret`
    directly.
 
-   Every example module in `mesh-control` had this wrong and shipped: `own-secrets` pointing at a
+   Every example module in `mesh-controller` had this wrong and shipped: `own-secrets` pointing at a
    path *named* `.env`, mounted as `env-file`, holding a bare password. Docker reads that as a
    malformed line and the container starts **with no password set at all** — not a failure to
    start, a service running on the wrong credential. They parsed and they resolved. Two tests in

00-META/process/07-feature-branches.md

@@ -1,7 +1,7 @@
 # Playbook 07 — Feature branches across repos
 
 **Trigger.** Work that changes code — in one code repo or in several at once (`mesh-sdk`,
-`mesh-control`, `mesh-catalog`, `mesh-host`, `mesh-lab`, and `hq` when a decision rides along).
+`mesh-controller`, `mesh-catalog`, `mesh-host`, `mesh-lab`, and `hq` when a decision rides along).
 
 **Who runs it.** Anyone who writes code, engineers and agents alike. Agents follow it exactly —
 it is the guard against the failure it was written for.