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

@@ -34,8 +34,15 @@ const GRANTS = "/var/lib/postgres/grants";
 const SUPER = "postgres://postgres:super@127.0.0.1:5432/postgres?sslmode=disable";
 
 let instanceId = "";
-/** The postgres image, by digest, from the registry the scenario raised. */
-let image = "";
+/**
+ * The database, pinned upstream and pulled by the machine over its uplink.
+ *
+ * The same digest the mesh's own postgres module pins, so this is the database the mesh runs
+ * rather than a lookalike. It used to come from a registry the lab raised inside the scenario;
+ * nothing outside the lab has one, so what that proved about fetching an image was true only here.
+ */
+const image =
+  "postgres@sha256:7456ef82e5f5bc43d997f4781bbd7c0d6389bff397564649a356e206ba473aee";
 
 function shellQuote(s: string): string {
   return `'${s.replaceAll("'", `'\\''`)}'`;
@@ -142,12 +149,6 @@ before(async () => {
   const instance = await raise(scenario, {});
   instanceId = instance.instanceId;
 
-  // From the registry the scenario raised, by digest. There is no route to a public registry from
-  // a documentation range, which is the point of the lab having its own.
-  const stocked = instance.images.find((r) => r.includes("postgres"));
-  assert.ok(stocked, `the scenario stocked no postgres image: ${instance.images.join(", ")}`);
-  image = stocked;
-
   await must(
     `docker run -d --name mesh-db -e POSTGRES_PASSWORD=super ` +
       `-p 127.0.0.1:5432:5432 ${image}`,