3 Commits

Include renames

Author	SHA1	Message	Date
mesh-toolsandClaude	de9d29dc65	Keep a group member's siblings and refuse its merge until the group passed and every sibling is reviewed (issue 867, ADR 0382) ... mesh-delivery's groups names each member's pull request, head, base and whether it is open (member_details), so the controller can read a member's siblings beside its check. The forge's holder keeps the siblings each verdict read, puts that verdict out of date when a sibling gets a new head, closes, or its base moves by anything but its own merge, and the merge tool merges such a member only when mesh/delivery-group passed at the heads read and each sibling head is approved. The statuses name the siblings, or say they could not be learned. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-15 23:27:13 +00:00
mesh-adminandClaude Opus 5.5	48f0662fde	Make the forge's tools act as an account of their own, not the administrator (issue 469, ADR 0365 clause 2) ... The tools' token reached everything the administrator may do, so their boundary rested on their own guards. The gitea module now makes a plain account, mesh-tools, with the admin login, gives it write on code, issues and pull requests of every novox repository through one team, and mints the tools' token for it; the admin's old token goes only after the new one is kept. The Go forge bundle sends that token, never the admin login. The forge shows protection rules only to a repository administrator, so every check reads a branch's protection from the branch. mesh-admin stays a ready author, so marks made before the move keep counting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 22:28:25 +00:00
jschoubben	434506f9b1	Serve the merge tool beside the one writer, and close the review's gaps ... The merge tool's pending bypassed the merge check's one writer from the tools' bundle (issue 456); it is now served beside it. A verdict no build judges names the announced base head, so the merge tool no longer refuses it for ever. A late verdict keeps its account, a trunk is read again in each head's turn so a fresh verdict is not put out of date, and a delivered member counts when a rebased member's group is composed again (novox/hq ADR 0323).	2026-10-12 17:46:39 +02:00