3 Commits

Include renames

Author	SHA1	Message	Date
mesh-toolsandClaude	37fd73f378	Check a delivery group's member beside its siblings' merges, judged by the group's controller (issue 867, ADR 0382) ... A mesh-host change and a mesh-controller change that need each other could not both pass their own checks: each read the other at its base. The check now asks mesh-delivery for the group's open siblings into a base of the same name, reads each at its head merged onto its base, builds the judge from a controller sibling's merge in the isolated judge environment keyed on its inputs, and names the siblings in the verdict. With no answer from mesh-delivery the verdict says it could not learn them; a pull request with no sibling is checked as before. TestReplay867 replays the failure. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-15 23:27:12 +00:00
mesh-adminandClaude Opus 5.5	2bee290eea	Keep judge builds warm in the build agent's judge cache, and leave nothing on the host ... Review of #329: a judge's home made with a temporary directory inside the build agent is resolved on the host by the container runtime, leaving a cold cache behind on every check, and a kept judge was lost on every redeploy. Judge builds now use the judge cache the build agent declares (MESH_JUDGE_CACHE), mounted into judge builds only: one warm Go cache, the kept judges, and a fresh home per check removed after it (hq ADR 0358 §6, issue 704, issue 482). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 13:53:05 +00:00
mesh-adminandClaude Opus 5.5	4a75cc51dd	Judge a pull request into a release branch by that branch's controller and repositories ... A release branch could never carry a change that needs another repository's release-branch change: its pull requests were judged by the running controller and against the other repositories' main (hq issue 704, ADR 0358). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 12:48:44 +00:00