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

03-DESIGN/01-to-be/09-the-node-lifecycle.md

@@ -6,8 +6,8 @@ code:
   - mesh-host internal/link/enrol.go
   - mesh-host packaging/nox-mesh-host-resume.service
   - mesh-host packaging/nox-mesh-host-network.sh
-  - mesh-control internal/token
-  - mesh-control internal/inventory/nodes.go
+  - mesh-controller internal/token
+  - mesh-controller internal/inventory/nodes.go
 updated: 2026-08-31
 decisions:
   - 02-DECISIONS/0004-a-node-and-how-it-joins.md
@@ -223,7 +223,7 @@ The same path, with the mesh built in the middle of it.
 nox-mesh-host reconcile
 
 # 2 — the controller now exists, and issues the first token
-mesh-control token issue
+mesh-controller token issue
 
 # 3 — the machine joins the mesh it just raised
 nox-mesh-host enrol --token <token>
@@ -548,8 +548,8 @@ rather than left to be worked out.
 **A token is issued *for* a node record**, and that is where a re-enrolment is decided.
 
 ```
-mesh-control token issue --node workstation   # this machine is that node again
-mesh-control token issue --new                # a machine the mesh has not seen
+mesh-controller token issue --node workstation   # this machine is that node again
+mesh-controller token issue --new                # a machine the mesh has not seen
 ```
 
 The host does not need to know which it is. It presents a token and receives an identity; what
@@ -629,7 +629,7 @@ keeps cataloguing.
 
 ### Where the enrolment token comes from
 
-**`mesh-control token issue` prints it once**, to the person running it. Single-use, and it
+**`mesh-controller token issue` prints it once**, to the person running it. Single-use, and it
 expires whether used or not ([ADR 0004](../../02-DECISIONS/0004-a-node-and-how-it-joins.md)).
 
 It is carried by hand — read off a screen, pasted into a terminal. That is the design rather than