Playbooks 07 and 08: mark ready with mesh-delivery.mark-ready, label then comment in the order the forge counts (issue 913)

2026-10-16 14:31:49 +02:00
parent 6dcfa2226e
commit 7b5f3582be
2 changed files with 5 additions and 3 deletions
@@ -159,8 +159,9 @@ controller part touched four files feature 57's release branch also changed).
   carries an integration test that starts the module whole, its process against the real bus and store, and
   shows the step's acceptance sentence; the forge's checks run it (ADR 0391 §1, §6). Unit tests alone are not
   that proof; the mesh has no end-to-end tests yet, and the lab is not used (the operator, 2026-10-16).
-5. **The reviewer marks each pull request ready as soon as the acceptance is shown** (`mesh/ready` and a
-   comment `ready at <full sha>`, the head it approved); mesh-delivery merges it when its checks pass
+5. **The reviewer marks each pull request ready as soon as the acceptance is shown** with
+   `mesh-delivery.mark-ready` (the delivery of the head it approved, who reviewed it and why), which writes the
+   label `mesh/ready` and then `ready at <full sha>`, the order the forge counts (issue 913); mesh-delivery merges it when its checks pass
   (ADR 0364). The operator's word is waited for only when the step changes what the operator sees, removes
   data, or needs a step only the operator's terminal can take; the lead says which before the step starts.

@@ -41,7 +41,8 @@ one delivery**. Everything before the push is local and fast.
   place they run (the operator, 2026-10-16). A failed check
   goes back to the same agent with the failure, and the reviewer reads only the change it makes.
 6. **The reviewer marks it ready at once** (for an edit that skipped the reviewer, the lead, on the
-   operator's word) (`mesh/ready` and `ready at <full sha>`, the head it approved);
+   operator's word) with `mesh-delivery.mark-ready` (the delivery of the head it approved, who reviewed it and
+   why), which writes the label `mesh/ready` and then `ready at <full sha>`, the order the forge counts (issue 913);
   mesh-delivery merges it when its checks pass. A fix to a module that changes how it runs carries an
   integration test starting the module whole against the real bus and store, run by the forge's checks
   (ADR 0391 §1, §6); unit tests alone are not that proof, and the lab is not used. The operator's word is waited for only when the fix changes what the operator sees, removes data,