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

00-META/glossary.md

@@ -47,8 +47,9 @@ another — and a mesh you cannot name precisely is a mesh two people describe d
 - **seat** — a named position at a scope (node / site / mesh) with a **capacity**. A capacity-1 seat
   is exclusive (one holder); a higher-capacity seat is a **bench** (several holders coexist).
 - **claim** — a module taking a spot on a seat. `claims: [{name, scope}]` in a manifest. A
-  mesh-scoped exclusive claim is how the mesh says "there is one of me" — e.g. `mesh-controller`
-  claims `the-controller`.
+  mesh-scoped exclusive claim is how the mesh says "there is one of me". A foundation seat is
+  named after the server it guards: the `mesh-controller`, `postgres` and `lavinmq` modules claim
+  the `mesh-controller`, `mesh-store` and `mesh-broker` seats ([ADR 0079](../02-DECISIONS/0079-the-foundation-seats-are-named-after-their-servers.md)).
 - **provision** — a service one module `provides` and others `require`; the mesh resolves a provider
   and wires the two with an endpoint and a credential. This is separate from seats: a provision is
   a service you offer, a seat is a slot you occupy.