5 Commits

Include renames

Author	SHA1	Message	Date
jochen	f4fb0a7461	Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363) ... Every merge to the controller's repository rebuilt the route proxy and the build seat's holder, because their builds read that repository whole. Named, the build seat hands each only its program's build source and the planner moves each only when that changes. A rename was said under its new name alone, so a file moved out of a build source changed nothing the planner could see.	2026-10-10 02:58:31 +02:00
jochen	685cb1cb1b	Declare every module's data; the backup holder measures it (hq ADR 0233) ... Backup lines are derived from each module's data section instead of written by hand; the holder measures declared items, reads the array under them, and deletes a retired item only after a last restore point; the Go providers say each held consumer's size so an empty replacement is seen.	2026-10-06 16:47:49 +02:00
jochen	0581256905	build-agent serves its seat's verbs: current, kill, pause, resume (hq ADR 0219) ... The node-build-agent seat now promises these verbs, and a holder that does not name them cannot hold it. The binary serving them is mesh-controller's cmd/mesh-builder; merge only once a controller carrying the seat's new verbs runs, since an older one refuses a claim naming verbs its row lacks.	2026-10-05 19:23:30 +02:00
jochen	02463ba55d	build-agent: a short slug, so its identifier on a machine fits a backend's 20-character key ... "mesh_novox_build_agent" is 22 characters; the mesh refused to send the control node its declaration for it. "agent" keeps the identifier within what an S3 access key allows on every machine.	2026-10-03 11:09:24 +02:00
jochen	84403aec0c	build-agent: the build machine as a node role every machine can hold (hq ADR 0190) ... The builder's manifest with one change that matters: it claims node-build-agent, a node seat, so it is assignable to every machine with a container runtime, and every holder pulls one build at a time from the role's one work queue. A tier of many images is then built by as many machines as hold the seat and are online. The builder module stays until this is assigned where it was; then it goes.	2026-10-02 22:28:48 +02:00