9 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	2d8ad2e66a	Checker: no candidate is left without a verdict (issue 1733) ... Once the gate's one-hour ask bound goes (mesh-catalog fix/1733-no-hour), the gate asks the operator's Approve only on a verdict, so every path that left a candidate without one now writes one, from an event and with no timer: - a group with a member whose repository's trunk head is not known (a pull request the checker cannot claim) is not judged in part: its verdict fails naming that repository, and every status of the group says so (a pass of the others would have let it merge with that member never checked); - the verdict of heads that cannot be judged replaces whatever the key held, such as a running verdict left by a check that can no longer run; - a verdict key deleted is judged again on its delete (the checker watches its verdicts), and a check running when its key is deleted writes it anew. Tests: three rows at the end of the no-trunk test; counts unchanged.	2026-10-28 21:50:03 +01:00
jschoubben	4e9b076408	Checker: say loudly that a pull request cannot be judged when its repository has no trunk head (issue 1422) ... A repository never merged through the gate has no entry in source.main, so its pull requests were dropped without a log line, a verdict or a status, and checker_status counted them as new. Now the verdict says it cannot be judged and why, the forge status is error with those words, checker_status names it under cannot_be_judged, the log says it once per head, and the heads are judged whole once the trunk head is known. Quick fix: this. Thorough fix (the gate seeding source.main from the pull message's base head) is still to do: it needs mesh-sdk, the forge bridge and the gate.	2026-10-28 11:03:39 +01:00
jschoubben	d95e9f3229	End a check whose heads no candidate holds, and start a group's check once its heads settle (issue 1890)	2026-10-26 21:44:12 +01:00
jschoubben	37860d46a0	Stop watching the node-engine's have in the checker: a check's asks wait in the build seats' streams, which redeliver a lost node's ask, so no check fails for want of a node; presence stays for an unheard forge and the assigner's presence (issue 1912)	2026-10-23 16:41:34 +02:00
jschoubben	69577f739d	Judge hq as any repository, so its pull requests get a verdict and mesh/check from its Go tests and no script judges it (issue 1887 A10, ADR 0527 §2)	2026-10-23 16:11:43 +02:00
jschoubben	d9d1e57e3a	Delete the checker's hold, its own capacity and places, its node moves and its read of the controller's plans-building, so a check waits only in the build seats' streams (issue 1887 A5b, closes 1685; ADR 0525 §4, §7)	2026-10-23 16:09:34 +02:00
jschoubben	f7d8622deb	Keep a core repository's passing package under a digest that covers its siblings' commits, so core checks keep verdicts (issue 1287, C3a/C3b, lead decision L5) ... The checker took and kept nothing for a workspace given siblings, and every core repository has siblings, so the kept store stayed empty. The digest step now folds the siblings' commits in and echoes them; a verdict is kept or taken only when the echo equals the siblings the fetch was given, so a digest that misses one never poisons another check (ADR 0444, issue 482).	2026-10-22 17:56:59 +02:00
jschoubben	96ba6bd3dc	Say the verdict in a line of at most 140 characters and owe the status mesh/check in the checker's bucket, which the forge bridge performs once per revision; the checker's stream checks wakes the readers of its buckets (issues 1682, 1683)	2026-10-21 21:20:42 +02:00
jschoubben	27072a01b5	Add the checker module: it watches the candidates, claims a verdict once, owes the status mesh/check and ends a check past its bound (issue 1678)	2026-10-21 21:07:14 +02:00