mesh-controller

3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ce9dc8e157	Run no hook and no signature setting when a check makes its merge mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it… Details mesh/repo-check pass: its merge-check.sh passed Details A build machine's or a clone's git configuration must not run code or change the merge a check judges (novox/hq ADR 0323).	2026-10-12 17:39:59 +02:00
jschoubben	25deb499bf	Say why a merge's changed files read as none on an error mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it… Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery superseded: a newer head of the same pull request Details	2026-10-12 17:31:36 +02:00
jschoubben	83a9cf6e3a	Judge a pull request's head merged into its trunk, and name the trunk commit A check judged the head alone, so two pull requests that each passed could break the trunk together (node-engine #66 on 2026-10-09), and a recheck after the trunk moved judged the same head again. The build seat now merges the head into the trunk's head in its own clone, never pushed, fails a head that does not merge cleanly naming the files, and the verdict names the head, the trunk commit and the commits read beside it, for the forge and mesh-delivery to weigh against the trunk's next move (novox/hq ADR 0323, issue 341).	2026-10-12 17:27:01 +02:00