mesh-controller

Author	SHA1	Message	Date
jschoubben	2134768dfe	The control plane prepares its own state, like any module Now that every parser on the mesh knows the word, the control plane's manifest says it. Its schema stops being a special case: the mesh derives the step from its own resource and gates its server on it, which is the failure of novox/hq 04-ISSUES/133 closed by the mechanism rather than by a hand-written step in one manifest.	2026-09-28 12:51:27 +02:00
mesh-admin	ef825688ee	Merge pull request 'The control plane learns 'prepares' one release before its manifest uses it' (#125 ) from fix/the-word-ships-before-the-manifest-uses-it into main	2026-09-28 10:49:36 +00:00
jschoubben	77a14360df	The control plane learns 'prepares' one release before its manifest uses it A manifest word has to reach every parser before a manifest carries it. The builder refused mesh-controller's manifest with `unknown field "prepares"` until it was rebuilt; then the running control plane could not read the manifest in the build result either, so the build was recorded with no module and the version never moved. Strict parsing is deliberate (novox/hq 04-ISSUES/003), so the word ships first and a manifest uses it next: this takes `prepares` back out of the control plane's own manifest, leaving the code that understands it, and the manifest says it again once this is running everywhere.	2026-09-28 12:49:33 +02:00
mesh-admin	9be2fb4750	Merge pull request 'A version prepares its state before it runs' (#124 ) from feat/a-version-prepares-its-state into main	2026-09-28 10:43:17 +00:00

Compare commits

Diff Content Not Available