mesh-controller

3 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	d984816844	Feature 57 (config and provisioning): release mesh-controller, the reviewed release branch merged with main, on top of main	2026-10-16 08:28:38 +00:00
jschoubben	5b455b8a24	Keep the first-machine gate behind a switch for walks begun before hq ADR 0360, and test both paths mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate head 5b455b8a2438 merged into trunk 76304d9db817 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang… Details mesh/repo-check head 5b455b8a2438 merged into trunk 76304d9db817 — fail: its merge-check.sh failed: --- FAIL: TestARenewalWrittenThoughItsAnswerWasLostIsSt… Details	2026-10-14 19:35:07 +02:00
jschoubben	da8a5e9bc0	Send a merge's builds to every machine at once, with no first-machine gate (hq ADR 0360) mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate head da8a5e9bc0f7 merged into trunk 76304d9db817 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang… Details mesh/repo-check head da8a5e9bc0f7 merged into trunk 76304d9db817 — fail: its merge-check.sh failed: --- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestA… Details The operator chose the leanest rollout: no gate, no one machine first, failures loud and fixed forward. A walk sends every rolled-out module to every machine running it in one step, built-by orders no tier, and a walk ends on its machines' reports. The backlog walk sends every machine at once and passes each on its applied report.	2026-10-14 19:19:49 +02:00