6 Commits

Include renames

Author	SHA1	Message	Date
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
jschoubben	b752b1f1df	Remove the release-branch judge from the controller, the wire and the build seat (issue 977, part A, ADR 0401)	2026-10-17 20:43:06 +02:00
mesh-toolsandClaude	151faa10a1	Judge a delivery group's composed check by the group's own controller, release branch included (issue 867, ADR 0239 §14) ... The composed check of mesh-controller#346 and mesh-host#114 into feat/57-config-and-provisioning was judged by the release branch's controller, which cannot build the node-engine member's validator, so the group could never pass. ADR 0239 §14 has the group's own controller judge when a member moves it; ADR 0358 §2 changes the judge only for a pull request into a release branch. A group member in mesh-controller now judges, with the mesh-host member's validator, built in the isolated judge environment and kept by content; the statuses say the group's controller judged. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-16 00:59:27 +00:00
mesh-toolsandClaude	3fdbea4204	Ask mesh-delivery for a recheck's group on a bus connection of its own (issue 867, ADR 0382 §1) ... `delivery check` runs as a command of its own, where no serving connection exists, so a recheck said its siblings could not be learned ("this controller is not on the bus") and mesh-host#114 was judged without its sibling. groupsAsked now asks through onTheBus, which lends the serving connection or dials one, as the hand-act log does. TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn drives the verb against a real responder. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-16 00:27:57 +00:00
mesh-toolsandClaude	de5292323f	Find a rechecked pull request's group by its repository and number (issue 867, ADR 0382 §1) ... A recheck rebuilds the pull request without its head branch name, so the sibling lookup found no group and said nothing: mesh-host#114's recheck was judged without its sibling. With no branch name, the group is the one whose member_details hold the pull request; an older mesh-delivery says the siblings could not be learned. TestReplay867Recheck replays it. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-16 00:13:06 +00: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