3 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	611113fc63	Test that a controller is judged with the validator it vendors and a node-engine member without a validator is judged all the same (issue 1391) ... The host member without validate/ failed first against the old judge ("holds no Go files", the validator could not be put in the judge); the controller member is judged by itself whatever the node-engine sibling brings; the group's judge is no longer keyed on the node-engine's validator.	2026-10-20 09:36:41 +00:00
jschoubben	66dc501fc4	Split the unit level from the integration level in cmd, builder, link, catalogue, inventory; cheap fixtures for the archive-entry bound, the registry waits and the catalogue copy (issue 895)	2026-10-17 21:32:23 +02:00
mesh-toolsandClaude	37fd73f378	Check a delivery group's member beside its siblings' merges, judged by the group's controller (issue 867, ADR 0382) ... 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