6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	245143d948	Build modules run at most as many steps as their node's build CPU gives, and say a check's phases ... Each of mesh-build-go, -node and -image declares cores-per-step (6, 2, 2) and hands it to the SDK puller, which bounds the configured capacity by floor(slice quota cores / cores-per-step), read live; thread limits and the status tools follow the effective capacity (issue 1806's follow-up: three Go checks on shanks' 12-core slice starved past the 30-minute step bound). mesh-build-go says its lint and test phases with the ask id (issue 1890).	2026-10-26 19:55:31 +01:00
jschoubben	8356d30e1b	Pull the Node build seat's asks beside the tools, delivery first and at most the node's capacity (issue 1887 A3node, ADR 0525 §2-§6)	2026-10-23 15:39:30 +02:00
jschoubben	3a25b6e1f8	mesh-build-node: push each done bundle to the artifact store from its own process and answer its reference (issue 1587, S5-S8, ADR 0498 §1 §2, lead decision L9) ... After the build ended the module pushes the packed bundle with mesh-sdk's PushBlob under <module>/<artifact> by its digest, a candidate's as a trunk build's, and the step answers artifact-store://<module>/<artifact>/blobs/<digest> instead of the archive's path. A push that fails fails the step not stored: <artifact>: <the store's words>; the packed bytes are never written to the node. The manifest requires artifact-store and places its address.	2026-10-22 18:25:14 +02:00
mesh-tools	983a6c39c8	Ship the Node build module's toolchain lock as an archive, not a template naming hosts (issue 1488)	2026-10-20 21:15:56 +00:00
mesh-tools	97ed21c250	Add the Node build module's toolchain lock, main, recipe, guard and key keeper (issues 1488, 1484), part 16 of 19	2026-10-20 21:01:26 +00:00
mesh-tools	3f6f8909d9	Add the Node build module's manifest, ssh files, toolchain package, build step and toolchain tests (issues 1488, 1484, 1490), part 15 of 19	2026-10-20 20:59:51 +00:00