Say the rehearsal is the only live check, and that a fix goes into main

The pull requests' checks still run before the walk, and by then the
release's branches have reached main. Name the silent machine too, and
list ADR 0360, which the passages rest on (review comment 12348).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

03-DESIGN/01-to-be/57-building-config-and-provisioning.md

@@ -9,6 +9,7 @@ decisions:
   - "ADR 0201"
   - "ADR 0113"
   - "ADR 0158"
+  - "ADR 0360"
   - "ADR 0362"
 ---
 
@@ -49,9 +50,10 @@ points at it.
 **What a release costs.** A proof that is run live (dunst on a workstation, a secret reaching its file, a
 database consumer connecting) is first seen in the lab rehearsal, and a fault found then holds the
 release, not one package. A merge's builds go to every machine at once (ADR 0360), so the release has no
-first node to hold it: the lab rehearsal is the only check before it reaches every node. A machine that
-fails to apply it, or whose provisioner reports a module's files failed (ADR 0362), is named in the walk's
-end and raises apply-failing, and is fixed forward with a new merge into the release's branches.
+first node to hold it: after the pull requests' checks, the lab rehearsal is the only live check before it
+reaches every node. A machine that fails to apply it, or whose provisioner reports a module's files failed
+(ADR 0362), is named in the walk's end and raises apply-failing, and one that says nothing within fifteen
+minutes is named silent; either is fixed forward with a new pull request into main.
 
 **Nothing breaks on the way.** ADR 0349 clause 17: each file is filled the old way or the new way, never
 both, by the form of its manifest, and the old forms stay accepted until the last module has moved.