5 Commits

Include renames

Author	SHA1	Message	Date
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	b7084a19e9	Build every judge where no pull request can reach, and never read mesh-lab at a release ... Review of #329: a judge built with HOME in the workspace runs git under a configuration a pull request's script can plant, so a hook could rewrite the judge's sources before they compile and the result be kept under an honest key (issue 482, issue 704). Every judge now builds with its own HOME, configuration and Go cache outside the workspace, no git configuration and no VCS stamping. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 13:30:46 +00:00
mesh-adminandClaude Opus 5.5	48b2906b5c	Keep mesh-lab at its trunk and build the release judge with a cache of its own ... Review of #329: mesh-lab's replays run with the container runtime's socket, so a same-named branch must never be what runs there; the shared Go cache and HOME are writable by a pull request's own script, so the judge kept for a head must not be built from them (issue 704, issue 482). A forge answer naming no branch is an error, and a trunk is the branch a repository follows, not a name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 13:13:30 +00:00
mesh-adminandClaude Opus 5.5	ea7d91bff1	Say which validator judged a release-branch check, and prove clause 5 ... ADR 0358 version 4 asks the verdict to say whether mesh-host's release-branch validator or the vendored one judged, and checks that a release branch's own pull request into its trunk is judged as any trunk pull request (issue 704). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 12:56:55 +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