4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	7618f661ea	Fail, not skip, when the checker places no controller beside the node-engine (issue 1295)	2026-10-24 03:43:49 +02:00
jschoubben	11b0a1fb29	Skip aloud the controller's step-nine check where the running checker places no controller (issue 1295, R4g)	2026-10-23 18:35:32 +02:00
jochen	b7f70bc4c0	Leave a file the controller's manifest writes itself out of genesis's secrets (hq issue 597) ... The controller reads its merge window's settings from a file its manifest declares from its settings (MESH_MERGE_WINDOW_FILE, ADR 0276). Step 11 took every MESH_..._FILE for a secret and refused this one as a file nobody writes, so no genesis got past step 11. A _FILE naming a file resource of the module is now the module's own; one naming neither an own-secret nor a file of the module is still refused.	2026-10-13 02:23:21 +02:00
jochen	d9ea387680	Raise a process-form controller at genesis as the container it replaces (hq issue 223) ... The controller's manifest now declares a Go bundle the host runs as a process (novox/hq issue 213). Genesis cannot run that: the bundle is fetched from the artifact store and compiled in a toolchain, and the mesh makes both long after the controller. The builder, asked to build the manifest at genesis, refuses for lack of the Go toolchain. So genesis raises the controller as before, as a container, and the first push hands it over to the process through `replaces` (issue 223, option b). - Step 3 clones the controller at the commit with the carried builder's git and reads its manifest. In the image form (an older controller) it builds through the builder as before. In the process form it builds the repository's own Dockerfile and hands step 9 a manifest of its own shape: the process becomes a container with the id the process `replaces`, the image genesis built, host network, and every host path the process's env names mounted at that same path read-only. Secrets belong to the image's user (65534) until the process's account takes them over. `prepares` is dropped: the temporary controller from the same commit already migrated the stores, and a pinned image is nothing the controller can derive a step from. - Steps 4 to 9 are unchanged: they take the manifest as they did. - apply.ForTests lets the bootstrap's test apply a process. The first composed declaration from the process manifest names `mesh-controller.server`, which is what the host recorded for the genesis container, so the first apply hands over and leaves one controller.	2026-10-04 01:47:33 +02:00