10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	b9cdca78b0	mesh-build-node: narrow the fetch to the named paths, build members against the SDK their lock names, and build, pack and publish a package (issues 1758, 1587 S15-S19; ADR 0499 §4, ADR 0498 §5, ADR 0500 §4-§6; lead decision L10) ... build_node_fetch takes buildstep.FetchRequest (dir and paths narrow the workspace) and an optional package {repository, commit, ref}: the group's package member, built and packed shut off and published nowhere. Each member's lock decides its SDK: the group's packed file when the version and integrity are the lock's, else the registry's (integrity checked); a version the registry lacks fails waits for: @novox/mesh-sdk@<version>. A package artifact is built by its own script and packed with npm pack, shut off; only a trunk build publishes it, from this process with the write credential (never in a workspace): absent is published, the same file is done, another is version taken:. The registry configuration file now lies outside every workspace.	2026-10-22 18:38:22 +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	710cfbd622	Merge pull request 'Let the build modules answer their own step results and toolchains, so a fetch's workspace and a build's digest can be read (issue 1562, build-module half)' (#410) from fix/1562-read-steps into main	2026-10-21 10:26:13 +00:00
mesh-tools	c33b83dce7	Read a build module's steps and toolchains states with its own tools, so a step's result and the reported toolchain can be checked live (issue 1562)	2026-10-21 09:57:16 +00:00
mesh-tools	bda75011a1	Say in the build modules' READMEs where the packages come from (issue 1573)	2026-10-21 09:50:55 +00:00
mesh-tools	e8046fca87	Say in the build modules' READMEs that they build with the installed toolchain, the digest holds no Go version, and the reference is agreement between build nodes (issue 1572, ADR 0477)	2026-10-21 08:05:55 +00:00
mesh-tools	c7e892ca63	Mark the build modules moved, so a machine assigned them composes before the forge serves their entry (issue 1537)	2026-10-20 22:59:36 +00: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	4a1804cda3	Review round 1 for the Node build module: build depth (1490), bin scripts for the test script (1491), toolchain.reported and its stream (1483, 1488); delta part 3 of 4	2026-10-20 21:10:18 +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