jschoubben dcdf4238c7 Build modules: no cap of their own; a step's threads are its part of the node's one share (ADR 0553, issue 1806) ...

Review round 1: a cap per module let three build modules take three shares
of the node. The share is now one node value held by the node-engine's
yielding slice; each step divides it by every build slot of the node, from the
composer's words, or assumes every build seat at its own capacity without them.

2026-10-26 14:22:05 +01:00

..

forge

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

gitconfig

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

known_hosts

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

registry

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)

2026-10-22 18:22:17 +02:00

settings.json

Build modules: no cap of their own; a step's threads are its part of the node's one share (ADR 0553, issue 1806)

2026-10-26 14:22:05 +01:00