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/assigned-vault.test.ts

@@ -22,7 +22,7 @@
  * The manifests are the catalogue's own (../mesh-catalog/modules/{mesh-vault,redis}/module.json), with
  * the runtime artifact named as the image the lab built, exactly as the other assigned-* beds do.
  *
- *   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
  *   scripts/build-module-runtime.sh mesh-vault / redis build the two runtime images into the local
  *   daemon; scenarios/vault-node.yml stocks them.
  */