10 Commits

Include renames

Author	SHA1	Message	Date
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	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	4ffe5f4d52	Start a never-judged head's check before the re-judges a trunk move asks, oldest first (issue 1897 S1) ... A new pull request waited 25 to 45 minutes behind every open pull request's re-judge after a merge. The semaphore becomes a ranked admission (ADR 0536 §4); checker_status names the waiting checks by kind.	2026-10-23 14:09:42 +02:00
jschoubben	2bdb8d0e00	Ask the Go build module to run the candidate when a merge changes it, and say in the line which program judged (issue 1898 K3) ... A change to mesh-build-go was judged by the installed module it replaces, so such pull requests were merged by hand. ADR 0535 §1, §2, §4, §5.	2026-10-23 14:06:57 +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	7abe230701	Judge a pushed head as a try on the checker, through checker_try and checker_try_read (ADR 0501 §5) ... mesh-controller's try asked build-agent, which leaves the checking at R4e. A try is now a key in the checker's state tries: the checker judges the head merged onto its trunk as it judges a pull request's head, through the same judge, places and holds, writes its end in the key and owes the forge nothing (no status, no preview, no verdict). One try per head, at most four at once; hq and a repository whose trunk the gate does not name are refused with "no level of <repo> is checked by the checker".	2026-10-22 18:03:28 +02:00
jschoubben	d9ace64681	Mark mesh/check pending on every open pull request into a moved trunk, and carry the gate's heads hash in each verdict (issue 1302's checker part, lead decision L4; issue 1300) ... The gate decides on mesh/check alone and matches an Approve's members by the heads hash over lowercase repositories and heads. A success judged on an old trunk stood on the forge while the next check waited for a place or a delivery, and a candidate whose repository the forge named in capitals carried a hash the gate never finds. A check that ends after its trunk moved now owes pending, not its verdict.	2026-10-22 17:58:49 +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	cfbd5b6d2d	Judge a head merged onto its trunk through the build modules: run only packages without a kept verdict, the change's own tests first, stop at the first failure (issues 1679, 1288, 1289)	2026-10-21 21:11:43 +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