A bed says what it actually needs to be pointed at

The instructions in every bed named the bundle that raises the predecessor's
broker, so a first attempt ends in a control plane crash-looping on a missing
MESH_BUS_NATS — which reads like a broken lab. They name the bundle that works
now, and the README says the host binary needs SYSTEM=arch, because one built
without it refuses everything with an empty system name.

And the three habits that each cost a run before they were adopted:
MESH_LAB_KEEP to leave the machine standing, MESH_LAB_WARM while iterating,
and rebuilding all three repositories the bed places rather than the one that
changed.

test/integration/openai-bed.test.ts

@@ -12,7 +12,7 @@
  * ordinary sealed-delivery path — with NO manager, NO refresh, NO access/refresh split, NO usage. The
  * whole of OpenAI's integration in the control plane is one registry line (vendor -> static-key).
  *
- *   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/foundation-first-node.lock
+ *   MESH_LAB_HOST_BINARY=.../mesh-host   MESH_LAB_BUNDLE=.../examples/foundation-first-node-nats.lock
  *   Build the consumer runtime image into the local daemon first:
  *     scripts/build-module-runtime.sh openai-consumer  /tmp/openai-consumer.tar
  */