Phase 3.2: lavinmq declares no network — it adopts mesh-broker

The V3 networking check asserted a `lavinmq` docker network exists, from the
two-server world. The module now adopts the foundation's broker rather than
raising its own on a private network (issue 051, WBS 3.2), so only the
consumer's own network remains.

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

test/integration/one-node-mesh.test.ts

@@ -848,8 +848,11 @@ before(async () => {
     said.push(`  names             ${(hosts.match(/[a-z0-9-]+\.internal/g) ?? []).join(" ")}`);
 
     // The networks the declarations asked for, rather than whatever the runtime had lying around.
+    // `lavinmq` no longer declares one: it adopts the foundation's mesh-broker rather than raising a
+    // server of its own on a private network (novox/hq issue 051, WBS 3.2), so the only module
+    // network here is the consumer's own.
     const networks = (await on(CONTROL, `docker network ls --format '{{.Name}}'`)).out;
-    for (const wanted of ["lavinmq", "amqp-ping"]) {
+    for (const wanted of ["amqp-ping"]) {
       assert.match(networks, new RegExp(`^${wanted}$`, "m"),
         `the ${wanted} module declares a network and none exists:\n${networks}`);
     }