novox/mesh-controller

Archived

Name what a held release holds, and where it is released (ADR 0258) #155

Merged

mesh-admin merged 2 commits from fix/release-held-says-what-waits into main

2026-10-08 15:09:29 +00:00

Author	SHA1	Message	Date
jochen	298ec06ae0	Say held updates wait because a walk failed, in the glossary's words 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 delivered Details The backlog is held after any failed walk, not only a release, and a check is a pull request's status; the words said the last release failed its check.	2026-10-08 17:02:30 +02:00
jochen	e33da2dc1c	Name what a held release holds, and where it is released 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 The release-held words said "release them, or leave them held" without the modules, the machines or the mesh MCP server, so the operator could neither tell what waited nor where to act (ADR 0258). The controller's restart needs missed the same suffix. A test now holds every need that opens with a verb only the mesh MCP server performs to name it, so a new kind cannot miss it.	2026-10-08 16:44:02 +02:00