The host's vocabulary is complete; 05 and 07 said otherwise

All six shapes are built. 07 still said the last three did not exist, and 05
still described stage 2 as having built three of six.

Records what the lab still cannot do, because that is now the only thing
between here and an end-to-end substrate bootstrap: a sealed scenario cannot
fetch an image and its machines carry no container runtime, so package,
container and action were verified against a real machine instead.

03-DESIGN/01-to-be/07-the-substrate.md

@@ -142,8 +142,9 @@ not a container. It is:
   [ADR 0046](../../02-DECISIONS/0046-the-installer-fetches-what-it-pins.md).
 
 So the host's bootstrap vocabulary is six shapes: **package**, **container**, **file**,
-**directory**, **service**, and **action**. Files, directories and services exist; the rest do
-not yet.
+**directory**, **service**, and **action**. **All six are built**
+([`05-the-node-host.md`](05-the-node-host.md) stage 2), so nothing in this bootstrap is
+blocked on the host any longer.
 
 **Steps 2 and 3 happen before there is a mesh to do them**, which is why provisioning is part of
 the bootstrap rather than a service consumers use later. They are **actions** the bundle