novox/mesh-controller
8
0
Fork 0
Code Issues Pull Requests 5 Releases Wiki Activity

Check a delivery group's member beside its siblings' merges (issue 867, ADR 0382) #348

Merged
mesh-tools merged 1 commits from fix/867-group-siblings into main 2026-10-15 23:53:02 +00:00
Conversation 4 Commits 1 Files Changed 12
+1277 -19
1 Commits
Author SHA1 Message Date
mesh-toolsandClaude 37fd73f378 Check a delivery group's member beside its siblings' merges, judged by the group's controller (issue 867, ADR 0382)
mesh/merge-gate head 37fd73f3781e merged into trunk 4446027108fd — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
Details
mesh/repo-check head 37fd73f3781e merged into trunk 4446027108fd — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
mesh/delivery-group group fix/867-group-siblings delivered: every member is delivered
Details 
A mesh-host change and a mesh-controller change that need each other could not both pass their own checks: each read the other at its base. The check now asks mesh-delivery for the group's open siblings into a base of the same name, reads each at its head merged onto its base, builds the judge from a controller sibling's merge in the isolated judge environment keyed on its inputs, and names the siblings in the verdict. With no answer from mesh-delivery the verdict says it could not learn them; a pull request with no sibling is checked as before. TestReplay867 replays the failure.

Co-Authored-By: Claude <noreply@anthropic.com>
 2026-10-15 23:27:12 +00:00