mesh-controller

6 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	013dad4688	Take the catalogue, overlay and validator from mesh-sdk in cmd/mesh-builder and cmd/mesh-controller, a to g (issue 1381, 1 of 6 import swaps) Swaps three import paths for mesh-sdk's go/catalogue, go/overlay and go/validate (the same packages, copied from this repository at `6c2a8d62`) and lets gofmt order the groups. The six swap commits compile together once the pin commit (go.mod, modules.txt) is on the branch; each alone does not, because a file on the SDK's types cannot call one still on the old package.	2026-10-20 08:22:07 +00:00
jschoubben	3834c72747	Find the delivery's owner on the controller's own path by the seat's claim, not its name (issue 1210)	2026-10-19 11:57:07 +02:00
jschoubben	675466a8c3	Hold the store tests' modules as the settle time did, and fault a dip after any healthy reading mesh/delivery delivered Details mesh/merge-gate head 675466a8c35f merged into trunk bff5b7f0e4f8 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 675466a8c35f merged into trunk bff5b7f0e4f8 — pass: its merge-check.sh passed Details Two tier tests relied on the two-minute settle to keep a module unjudged; the witness window and the gate's spacing now hold it. A healthy reading taken before the controller's floor counted no pass, so a dip after it did not take the two-minute pass away (novox/hq ADR 0352 decision 3).	2026-10-13 23:07:15 +02:00
jschoubben	41eefc2f8c	Test that a healthy node-engine passes at two minutes on one reading mesh/merge-gate head 41eefc2f8c3e merged into trunk bff5b7f0e4f8 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 41eefc2f8c3e merged into trunk bff5b7f0e4f8 — fail: its merge-check.sh failed: --- FAIL: TestACoreBehindWhileTheNodeToolsSettleFailsNo… Details mesh/delivery superseded: a newer head of the same pull request Details	2026-10-13 22:58:37 +02:00
jschoubben	c3946e5d72	Pass the node-engine and resolver on their third reading, at most two minutes mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate head c3946e5d72c2 merged into trunk bff5b7f0e4f8 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head c3946e5d72c2 merged into trunk bff5b7f0e4f8 — fail: its merge-check.sh failed: --- FAIL: TestACoreBehindWhileTheNodeToolsSettleFailsNo… Details The operator wants these gates as fast as they can be: counting readings only after two minutes added about 80 s to every node-engine rollout for no safety. Count from the send, pass on the third healthy reading, and pass a module healthy at every reading at two minutes on what it has (novox/hq ADR 0352).	2026-10-13 22:55:46 +02:00
jschoubben	524295926f	Pass the controller's first-node gate on one reading after the witness window mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate head 524295926f76 merged into trunk bff5b7f0e4f8 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 524295926f76 merged into trunk bff5b7f0e4f8 — fail: its merge-check.sh failed: --- FAIL: TestACoreBehindWhileTheNodeToolsSettleFailsNo… Details The controller runs on one machine, so three readings over two minutes guarded no other machine and held every walk behind it. Judge each module by its own rule: one reading for the controller and the tool runner once the node-engine's witness window has ended, one for mesh-delivery, three for the node-engine and the resolver with the first two minutes after the send (novox/hq ADR 0351). The gate's verdict names the rule it applied.	2026-10-13 22:39:32 +02:00