diff --git a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md index bdeb730c..a2da7ba7 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md +++ b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md @@ -690,3 +690,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | The tool runner's own pipeline (rows 169 and 170) passed after the composition's rerun, and at 19:28:13 the holder of the seat mesh-wants wrote the tool runner's want on every node (the operator's desktop, the laptop, the home server and the control-node) at the new fingerprint and release 0.1.56, step passed-pipeline (read by the lead at 19:30 through the assigner's reasons tool); the mesh MCP server dropped for a minute at 19:29, as the tool runner on the operator's desktop restarted with the new release; the node-engines' start of the new release on each node is being read, and is row 172's. From the probe merge at 19:13 to the wants: fifteen minutes, the rerun's three minutes inside them. This is the delivery part of proof 2 (row 167); the one-call merge of the SDK and the tool runner was row 136's (rows 136, 167 and 170); the holder of the seat mesh-wants (`mesh-delivery-assigner`) and the tool runner (`node-tools`). | H1 | | The node-engines applied the tool runner's new composition on every node within thirty-five seconds of the wants: the laptop at 19:28:36, the control-node at 19:28:42, the operator's desktop at 19:28:46 and the home server at 19:28:47, each restarting the tool runner because its bundle and its fingerprint changed, and reporting the new build healthy within twenty seconds (the build digest the node-engines report, 0a11dca2…, is the one the builder published as release 0.1.56 at 19:15); the control-node's node-engine had waited a minute for the composition ("the composer has made none yet", 19:27:43), the no-responders episode of row 170. Proof 2 is shown: the SDK and the tool runner merged in one call (row 136, 12:26), the tool runner running everywhere at the new SDK release by its pipeline (rows 167 to 172), no hand act on its path, and the day's hand packs all on the delivery system's own parts (rows 136, 167 and 171); the node-engine and the tool runner (`node-tools`). | H1 | | The lead's statement (lead-47, on the operator's desktop, 19:31): the freeze on hand placing of the delivery system's parts is lifted (step 8). Both proofs of the runbook's step 7 are shown; every part of the delivery system now runs a build its own pipeline delivered or, where a hand pack of today still runs (the pipeline runner, the builder, the indexer, the assigner, the tool runner, the private network module and the store module, named in rows 134, 148, 160 and 166), a build whose source is merged on main and whose pipeline has passed or runs. From now a change to any part is delivered by its pipeline only, and a fault met is fixed in its repository and delivered the same way; the operator's rule of 2026-11-16 on probe merges ends with this statement. The merge of the change of the assigner and the runner (row 146) waits on the operator's word only because the permission check of the lead's session refused the dispatch, not as a decision. What H1 leaves to H2 is the owed list across rows 150 to 170; the runbook. | H1 (done) | +| Step 8's tail: the two issues the milestone ran under (one held module holds every reader's version back; a change across the SDK, the controller and the catalog repository needs three releases) were resolved at 19:33 with the proofs as the live case, and the second one's last open note (the indexer's dry run of a branch writes that branch's packages into the live packages state the trunk reads) was carried into H-A-297 as owed work. The recovery-mode rules of 2026-11-15 and 2026-11-16 on the lead's side ended with the freeze. The lead's dispatch of two reviewed merges, the change of the assigner and the runner (row 146) and the teller's test fix (row 170), was refused by the lead session's permission check, so both wait on the operator's word and are not routed through another agent; the catalog repository's two test fixes (rows 165 and 170) merge as one call; this branch's pull request is being opened for hq's check (rows 146, 170 and 173); the indexer (`mesh-delivery-indexer`) and the runbook. Owed: H-A-297 (a dry run reads and writes only its own scratch state, and leaves the trunk's packages state untouched). | H1 (done); H2 (the dry run) |