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/checks/records.py

@@ -293,7 +293,7 @@ def check_status_against_code(failures):
 
     Deliberately weak, and that is the point of it being mechanical. It cannot tell whether the
     prose is true, only that a document has stopped claiming to be unbuilt once it points at
-    something. `code: [mesh-control]` — a repository with no path — is a plan and stays
+    something. `code: [mesh-controller]` — a repository with no path — is a plan and stays
     `designed`.
     """
     for path in markdown_files():