3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	aac4bae5a4	A group member's own check runs its repository's check alone, a cycle fails the composed check, and mark-ready leaves the delivery seat (issue 977, part D, ADR 0403)	2026-10-17 21:22:55 +02: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