13 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4026f6c188	checker: a check is never held by a turn its own heads wait in, the node-engine read at its running commit is named and carried when it moves, and a gate bucket made after the start is opened before the next claim (ADR 0548 §3, §6; issue 568, review round 1)	2026-10-26 12:14:50 +01:00
jschoubben	5fed429827	checker: a verdict names the siblings it read at their trunk, and a sibling's move is carried as a trunk move is (ADR 0548 §6; issue 568 D4)	2026-10-26 11:33:35 +01:00
jschoubben	65496fc4f7	Merge main into feat/r4g-finish, keeping #37's same-branch mesh-sdk pin rule beside the node-engine check's controller placing (issue 1295)	2026-10-24 21:54:46 +02:00
jschoubben	991589fdd2	A try of a branch accepts a mesh-sdk pin at the head of mesh-sdk's branch of the same name, so a milestone's repositories can be tried before their pull requests (issue 1921)	2026-10-24 16:41:39 +02:00
jschoubben	840e56eddb	Fail the node-engine's check when the controller's trunk is unknown, so its step-nine test never skips (issue 1295)	2026-10-24 03:43:49 +02:00
jschoubben	b2c545c40a	Place mesh-controller beside the node-engine's tests, which read its manifest (issue 1295, R4g)	2026-10-23 18:36:13 +02:00
jschoubben	e4b639c6de	Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4)	2026-10-23 16:05:55 +02:00
jschoubben	4c98841d2a	Judge a repository the mesh knows no module of with both build modules, so mesh-lab's nested Go modules and its npm test both run (issue 1887 A12)	2026-10-23 15:41:57 +02:00
jschoubben	0f7091e4ac	Place the change's own repository beside it at its trunk, so a shrink-only list test compares with the trunk's copy at $MESH_CHECK_BESIDE/<name> (issue 1887 A12, ADR 0529 §2)	2026-10-23 15:35:37 +02:00
jschoubben	7d740be255	Fail a check whose forge read reached nobody at the forge, and judge it again when the nodes change (issue 1624, C7) ... mesh-catalog #293 failed with 'go.mod cannot be read to check its mesh-sdk pin: nats: no responders', put at the build node, and stayed failed: the forge's tool runner was not answering for a moment, which is not the change's failure. The forge's reads now mark such a call unheard, as the build steps' calls are (issue 1820).	2026-10-22 18:07:22 +02:00
jschoubben	14c78e485f	Read a Go module's go.mod at the trunk when the head does not hold it, so a branch cut before the module was added passes the pin check (issue 1845)	2026-10-22 15:00:58 +02:00
jschoubben	b519c8dde2	Keep nothing for a workspace given siblings, place the siblings where the tests state them, decide the hold from the listed plan keys (review D1-D3)	2026-10-21 21:52:41 +02:00
jschoubben	a20af30d54	A group's Go member naming a mesh-sdk commit that is neither on the trunk nor the group's head fails the check naming the member and the commit; a pin only a head carries names issue 1148 (issue 1624)	2026-10-21 21:34:35 +02:00