3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	db937546ae	Pull the Go build seat's asks beside the tools, delivery first and at most the node's capacity, so no part chooses a node for a Go build or check (issue 1887 A3go, ADR 0525 §2-§6)	2026-10-23 15:33:24 +02:00
jschoubben	b6247f837d	mesh-build-go: push each done archive to the artifact store from its own process and answer its reference (issue 1587, S1-S4, ADR 0498 §1 §2, lead decision L9) ... After the build ended the module pushes the packed bundle or archive 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 a 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:22:17 +02:00
mesh-tools	298a0b8eda	Test the forge account provider's builder entries, and add the Go build module's manifest, ssh files and README (issues 1481, 1483), part 6 of 17	2026-10-20 20:48:52 +00:00