The beds name images the way a machine would find them

Twenty-eight integration tests each carried their own copy of the same two helpers,
which pointed a manifest and the substrate bundle at whatever the lab's registry had
assigned. They now share two in the harness, and the difference is the point: ours is
rewritten to the ID the machine holds it under, and everything else is left exactly as
written so the machine pulls it.

**The substrate bundle is where the fiction was most load-bearing.** mesh-host's
`examples/substrate-first-node.lock` pins all three of its images at
`192.0.2.250:5000/…`, which is the address the lab's registry served from — it was
written for a target, and the target was the lab. Two of those are ordinary third-party
images and become the digests mesh-catalog's own postgres and lavinmq modules pin, so
the substrate's store and broker are literally the images the mesh runs. mesh-control
exists in no registry at all and becomes the ID the machine was handed. **The bundle
itself should be fixed in mesh-host and this substitution deleted with it.**

Beds that wrote a manifest by hand named an image by repository and let the rewrite
supply a digest. There is nothing to supply one now, so `onTheMachine` refuses an
unpinned reference and hands back the digest the catalogue pins — a bed runs the image
the mesh ships, and a bed that drifts from the catalogue is testing a different
postgres.

Three beds took a third-party image out of the raised list, which no longer contains
one: certificates (pebble), objectstore (minio and its client) and provisioner
(postgres) now name theirs and pull it. builds and mesh publish into the MESH's own
artifact store — the `registry` module's image, on the node, on 5000 — rather than into
scenery the lab raised. That is a different claim, and only one of them exists in
production.

New unit tests cover what a full raise would otherwise be the only way to check: the
routes an egress machine gets (that its gateway is still the path to the rest of the
scenario, that a range with no path is unreachable rather than leaked to the uplink,
that each family gets its own next hop), which machine is handed which of our images,
and the `images:` rule that refuses a third-party entry. The "shipped scenarios are
valid" test now loads every scenario rather than two of them.

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

test/integration/certificates.test.ts

@@ -32,6 +32,14 @@ const SCENARIO = "a-public-name";
 const MACHINE = "anchor";
 const NAME = "photos.example";
 const ACME = "/var/lib/acme";
+/**
+ * The ACME server under test, pulled by the machine over its uplink.
+ *
+ * It used to be served from a registry the lab raised inside the scenario. Nothing outside the lab
+ * has one, so an image only reachable there was a fiction — and this test is about a certificate
+ * being obtained over a real path.
+ */
+const AUTHORITY = "ghcr.io/letsencrypt/pebble:2.5.0";
 
 let instanceId = "";
 
@@ -59,8 +67,7 @@ before(async () => {
   const instance = await raise(scenario, {});
   instanceId = instance.instanceId;
 
-  const pebble = instance.images.find((r) => r.includes("pebble"));
-  assert.ok(pebble, `the scenario stocked no ACME server: ${instance.images.join(", ")}`);
+  const pebble = AUTHORITY;
 
   await must(`mkdir -p ${ACME}/cache`);