ADR 0079: foundation seats are named after their servers; issue 056 resolved

The store and broker were "one per mesh" by convention only. Each foundation module now
claims a mesh-scoped seat named after the server it guards — postgres/mesh-store,
lavinmq/mesh-broker — and the controller's seat is renamed the-controller -> mesh-controller
so all three follow one rule. The resolver refuses a second holder, closing 056. Glossary,
the foundation and installation docs, and the decisions index follow the new name.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

03-DESIGN/01-to-be/07-the-foundation.md

@@ -8,10 +8,11 @@ code:
   - mesh-catalog modules/postgres
   - mesh-catalog modules/lavinmq
   - mesh-lab test/integration/mesh.test.ts (a bare machine becomes a mesh)
-updated: 2026-09-16
+updated: 2026-09-17
 decisions:
   - 02-DECISIONS/0004-a-node-and-how-it-joins.md
   - 02-DECISIONS/0078-the-store-and-broker-are-modules.md
+  - 02-DECISIONS/0079-the-foundation-seats-are-named-after-their-servers.md
   - 02-DECISIONS/0077-the-controller-and-the-foundation.md
   - 02-DECISIONS/0005-the-node-host.md
   - 02-DECISIONS/0006-the-substrate-and-the-control-plane.md

03-DESIGN/01-to-be/21-the-installation-in-full.md

@@ -131,7 +131,7 @@ two.
 |---|---|---|---|
 | 1 | `postgres` | `postgres-database` | **the controller's own records and every module's.** One server, not two |
 | 2 | `lavinmq` | `amqp` | the broker every node dials, and what modules are granted vhosts on |
-| 3 | `mesh-controller` | *claims* `the-controller` | decides what runs where |
+| 3 | `mesh-controller` | *claims* `mesh-controller` | decides what runs where |
 | 4 | `distribution` | `artifact-store` | what the mesh built, pinned by digest — the module is the software (Distribution), the provision is the job |
 | 5 | `builder` | — | turns source into artifacts |
 | 6 | `mesh-tools` | build inputs | the base everything with code compiles against. **Runs nowhere** |