Design 47 H: section 10, finding 171

This commit is contained in:
2026-11-21 19:31:10 +01:00
parent 7d2715aef9
commit 81cb834991
@@ -687,3 +687,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again
| The forge module's six failures (row 167) are one test: its whole-seat test over a real bus, added on 2026-11-20, needs the module's npm packages installed, which the Go integration step never has (it fetches the tree without network), so it has never passed in a pipeline and sank every pipeline carrying the forge since, the one of 15:03 (row 143) included; the forge module and the Go build module (`mesh-build-go`). Settled by H-A-294 (a test that needs tooling its step lacks checks its needs first and ends NOT RUN with the reason and where it was proven, the build module's own precedent), in build in the catalog repository. The probe merge of row 167 landed at 19:13 and became a pipeline of one mover, the tool runner, being watched. The first of the four test fixes is built: the private network module's three tests read their facts from copies in the package's own test data, held equal to the originals wherever the repository is whole; the cause was the artifact's declared paths holding only the module's Go directory (rows 143, 165 and 167). Owed: the Go integration level receives a module's npm tree behind a declared need, and a read tool for a run's test output, which answers nothing through the mesh MCP server today. | H1 (the fixes); H2 (the need and the tool) |
| The tool runner's own pipeline (row 167) waited its turn behind the running ones and was placed at 19:20 with eight steps; the fixed builder (row 166) had built and published the tool runner's release 0.1.56 at 19:15, before the pipeline's turn came, the publish sent by the publish-again path within a minute of the build's end. The first test fix (row 168) went to a second review round: it cited an issue instead of its design line (A-474, a module's tests read nothing outside their module), and its drift guard compared the copies against the sibling module's tree, which that line forbids; the guard now holds only the module's own manifest, and the contracts module's facts are proven against copies without a guard (rows 166, 167 and 168); the pipeline runner (`mesh-delivery-pipeline`), the builder and the private network module. Owed: the facts' home is a test in the contracts module. | H1 |
| The tool runner's own pipeline (row 169) ended failed at 19:21 in its composition step: the compose ask met no responders on the node-engines of three nodes at once, while every node-engine answered discovery three minutes later; the lead ran the step again at 19:25 with the pipeline runner's rerun tool, and H-A-296 settles the kind (a seat ask that meets no responders is asked again with a back-off until its bound, never a verdict at once). The remaining three test fixes are built: the teller's test bed now answers the seat-holder ask the live mesh answers (the fault was the bed's, five of seven pipeline failures today), and on the way a live fault of the teller was fixed (two takers of one event since the SDK's views reader took its bare subject; H-A-295 keeps the ask-again for want of room until A-424 is built); the zfs module's test race is fixed, with a real fault of its client beside it (a peer not root whose write was cut was never told "only root"); and the forge's whole-seat test ends NOT RUN when its npm tooling is missing (H-A-294) (rows 165, 168 and 169); the holder of the seat mesh-wants (`mesh-delivery-assigner`), the pipeline runner (`mesh-delivery-pipeline`), the teller, the zfs module, the forge module and the Go build module. Owed: the no-responders wait in the assigner's composition run and in the runner's asks, and the step's own NOT RUN summary in the Go build module. | H1 (the fixes); H2 (the no-responders wait, the step summary) |
| 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 |