No ready mark: the Approve is asked once the checks pass, and a group merges in one pass on its one Approve (issues 1022, 978) #352

Merged

mesh-tools merged 4 commits from feat/one-group-one-plan into main 2026-10-17 20:11:06 +00:00

Conversation 5 Commits 4 Files Changed 51

+1474 -2734

4 Commits

Author	SHA1	Message	Date
jschoubben	0771797431	Merge remote-tracking branch 'origin/main' into feat/one-group-one-plan	2026-10-17 21:40:08 +02:00
jschoubben	47e42806ff	Leave a composed member's gate to the group's verdict, reword the mark leftovers, restore main's merge-check.sh (issues 1022, 978)	2026-10-17 21:33:03 +02:00
jschoubben	2d3b61ec45	Merge a group in one pass on its one Approve, with no order and no turns (issue 978) ... A group has no order: mesh-delivery asks the controller for none, reads no after: line (it says once that the line is not read), merges every member in one pass once the composed check passed and the Approve covers the heads, and gives the plan its word once every member is merged. A failed member stops no other. The composed verdict sets each member's mesh/merge-gate (pending, saying why, until one stands), the groups answer says composed_gate, and a trunk move asks the out-of-date members' checks at once and merges on the same Approve (issue 1047).	2026-10-17 20:54:16 +02:00
jschoubben	668444785d	Ask the Approve as soon as the checks pass, with no ready mark (issue 1022) ... The review finishes before the push and its record is a Reviewed-by line in the description, so the mark repeated what the push meant. mesh-delivery asks the operator when a pull request's checks pass, keeps an ask through a trunk move by asking the check again at once, and hands the merge tool the approved heads, which replace the forge review of each sibling.	2026-10-17 20:44:54 +02:00