Scenarios: egress where images are needed, and images: cut to what is ours

Every scenario that places a container runtime gives each of its machines
`egress: true` — a node that runs modules pulls images from the internet, which is what
a node does. The underlay-only scenarios (bootstrap-single, behind-nat,
segmented-and-unforwardable, the-ordinary-shape, two-on-a-segment) stay sealed on
purpose: an extra NIC would change the very reachability they are asserting about.

`images:` keeps only the mesh's own — 55 third-party entries leave whole-mesh-full
alone, and the machine fetches them itself by the digest its module.json already pins.
The whole-mesh beds also say per machine which of ours they get: novox the substrate
control plane and its own fifteen runtimes, ace its twenty-four, the two workstations
one each. That is not a lab economy. An operator's workstation holds the images its own
modules need, and giving these two the union would put some thirty gigabytes onto a
thirty-gigabyte disk.

bootstrap-with-registry.yml is deleted. It existed only to demonstrate the lab's
registry, nothing referenced it, and there is nothing left for it to demonstrate.

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

scenarios/model-usage-bed.yml

@@ -25,25 +25,23 @@ machines:
   # The substrate ONLY: store, broker, control — three containers.
   anchor:
     at: { segment: hosting, address: [192.0.2.10] }
+    egress: true
     inbound: allow
     memory: 4GiB
     cpus: 4
   # The postgres PROVIDER (server + broker-bound runtime) and the model-usage CONSUMER (its run-once
   # migrate and its long-lived event runtime). The 5432-vs-substrate conflict is gone because the
   # substrate store is on the OTHER node. The runtime images plus postgres:17-alpine are pulled from
-  # the scenario's own registry by digest; forty gigabytes holds them with room to spare.
+  # the internet over the uplink; forty gigabytes holds them with room to spare.
   laptop:
     at: { segment: hosting, address: [192.0.2.20] }
+    egress: true
     inbound: allow
     memory: 4GiB
     cpus: 4
     disk: 40GiB
 
 images:
-  # The first-node substrate: store, broker, control. postgres:17-alpine doubles as postgres's own
-  # service image.
-  - postgres:17-alpine
-  - cloudamqp/lavinmq:latest
   - mesh-control:development
   # The per-module runtimes, built by scripts/build-module-runtime.sh and stocked here. Each carries
   # its module's code — postgres its provisioner, model-usage its consumer, tools and run-once migrate.