Phase 3 closed — the store and broker are ordinary modules, issue 051 fixed

Marks WBS 3.2/3.3/3.4 done and resolves issue 051: the foundation's store and
broker are adopted in place as the postgres and lavinmq modules, upgradeable
through their stated windows, source-tracked by status. A bare-metal mesh runs
one postgres and one lavinmq, proven 22/22 in the one-node lab. The two follow-up
gaps are tracked as issues 054 and 055.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

03-DESIGN/01-to-be/22-the-work-ahead.md

@@ -87,11 +87,19 @@ a protocol that agrees, a registry to publish to. Issue 051.
       binds `0.0.0.0` from genesis so a mesh consumer can reach it, but the packet filter is
       installed later — a brief pre-filter window where `mesh-store` is open before `from: mesh`
       clamps it; bring the filter up earlier or bind narrower at genesis.)*
-- [ ] 3.2 the broker is adopted — one `lavinmq`, the `/` vhost for the mesh bus, a vhost per
-      consumer that requires `amqp`; the second server gone
-- [ ] 3.3 an upgrade of each, proven: a store the controller reads from, a broker over the
-      broker, each with a stated window
-- [ ] 3.4 `status` can say the foundation is behind its source, which today it cannot form
+- [x] 3.2 the broker is adopted — one `lavinmq`, the `/` vhost for the mesh bus, a vhost per
+      consumer that requires `amqp`; the second server gone. *(Adopted in place like the store; the
+      module names mesh-broker with the foundation's TLS spec, the provisioner runs host-networked
+      as lavinmq's default guest, amqp-ping reaches it. Proven 22/22.)*
+- [x] 3.3 an upgrade of each, proven: a store the controller reads from, a broker over the
+      broker, each with a stated window. *(Lab steps S1/S2: move each module's source, build, roll
+      out, then a full push applies the server change and recreates the container. The store's
+      window is a pool reconnect; the broker's is longer — recreating the bus the push travels over,
+      so the mesh reconnects to the one that returns. Data survives on the named volumes.)*
+- [x] 3.4 `status` can say the foundation is behind its source, which today it cannot form.
+      *(Given by the adoption: postgres/lavinmq are ordinary modules with a source now, so
+      `module list`/`status` reports them behind or current like any other — the question could
+      not form when they were bundle containers.)*
 
 **Done when.** A mesh built from bare metal runs one postgres and one lavinmq, and can upgrade
 either — so the twelve-module floor has no specialty left in it.