Say in to-be 47 that a covered stop reads covered and stays listed, and that a one-machine module is covered (issue 480)

03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md

@@ -103,7 +103,11 @@ delivery merged with no walk answering it within ten minutes is held too, with t
   forge says that later merge commit contains it (`gitea_contains`, asked once per pair and kept). Merge
   order is only the first filter, and a forge that cannot answer means not yet covered. `mesh/delivery`
   says `covered: a later merge that contains it was delivered` as a success. A module that runs on one
-  machine only gets no "rest" step and is never covered;
+  machine only is covered too: its walk records the empty rest as sent once its first machine passes
+  (ADR 0270, as corrected 2026-10-12);
+- *a stop whose walk ended without building its modules* (issue 474) stays `stopped`, a final state, and
+  is read as covered once a later merge covers it by the same test: `mesh/delivery` then says `covered after
+  its stop` with the covering merge, once, as a success. No state or transition is added (issue 480);
 - the covered row is tried before `go`, from `held` and from `ready` past the ten minutes.
 
 **History is retired, not held** (ADR 0250).
@@ -334,7 +338,7 @@ In this order, each by its owner:
 
 | Verb | Answers or does |
 |---|---|
-| `deliveries` | every delivery not final, and the final ones of the last day, one line each; filtered by state, repository or group |
+| `deliveries` | every delivery not final, the final ones of the last day, and every final one `stalled` still lists, one line each; filtered by state, repository or group |
 | `show` | one delivery or group whole: plan, transitions, machine steps, order, the walk |
 | `groups` | every group with its members in order and its derived state |
 | `what-if` | the delivery plan a diffset would have, asked of the controller's planner, kept nowhere |