Phase 1.3 done: ordering was already there, the network was not

Ordering needed no change for the third time running — resources apply
in the order declared and nothing sorts them — and is now asserted,
because sorting them for any sensible reason would have passed every
other test.

Separates ordering from readiness, which the task had run together: a
container started is not a container ready. Nothing waits, and what
needs something usable retries. That is deliberate and more robust than
start ordering, since a dependency can restart long after apply.

The network was the first thing in Phase 1 that genuinely needed
building, and the first that needed a decision: 0029 records why a shape
rather than an action, and the vocabulary is nine.

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

@@ -194,7 +194,7 @@ So the bootstrap uses four shapes: **package**, **container**, **service** and *
 *counted from `substrate-first-node.lock`, which is the only bundle there is*. It had said six,
 adding `file` and `directory`, which this bootstrap never asks for.
 
-All four are built, as are the host's other four
+All four are built, as are the host's other five
 ([`05-the-node-host.md`](05-the-node-host.md) stage 2), so nothing in this bootstrap is blocked
 on the host any longer — which is the claim that mattered, and it was true either way.