Playbook 07: the build seat's holder, not a retired word (review of #405's check)

2026-10-17 17:56:21 +02:00
parent 0e7eb9c2da
commit 06440c1522
1 changed files with 1 additions and 1 deletions
@@ -145,7 +145,7 @@ never into the running one, unless it blocks the running one.
 3. **A check that fails** goes back to the reviewer with the failure, for **one more cycle** of phase 2 with
   the same fixing agents; then push once again. **The failure is read from the check's whole log**, never
   reasoned from its summary: `mesh-delivery.show` names the check's build id, and `mesh-controller.builds` with
-   `log` set to that id prints everything the build machine said. A check's summary picks only some failing lines;
+   `log` set to that id prints everything the build seat's holder said. A check's summary picks only some failing lines;
   on 2026-10-17 it showed a store test's `FAIL` without its cause, and a fix was first guessed from the code.
   **A change to `merge-check.sh` is judged by main's version of it**, so a test the change adds must pass under
   either version: one that runs the new script's behaviour runs a file of its own, never `merge-check.sh` itself.