5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	eff81f1220	Never refuse a node for a held module's stand-in by its own runtime's rules (issue 774) ... On 2026-10-30 at 21:04 mesh-self-check (ace) and mesh-conditions, mesh-healers (novox) were placed before their bus accounts were issued. Each was held for "needs a secret called broker and none was made"; its bare stub then lost its own secrets and was refused by ownRuntimes ("runs as its own account and declares no own secret broker"), a refusal no culprit takes, so 74 modules on ace and 79 on novox failed. A held runtime's stub met the same kind earlier today ("its build produced 0 bundle(s)"). Quick fix: let the bare stub keep its broker own secret, for this one rule. Thorough fix (chosen, the fourth of the kind today): a held module's stand-in (Stubbed) has no runtime composed at all, so no rule about its runtime, bundle or broker can refuse it: ownRuntimes passes it over and runtimeProcess composes none for a held runtime (what runs of either is carried, as before). A module of its own account left without its runtime by a held runtime is refused with a typed NoRuntimeToRunError, which makes the held runtime the culprit, so those modules are held after it and the node composes the rest.	2026-10-30 21:18:06 +01:00
jschoubben	6ac8c5c229	The composer gives a build seat's holder its node's one share, the node-engine's build-cpu-share (ADR 0553 §3, §4) ... The second half of ADR 0553, merged only once the node-engine that decodes yields runs on every node (§5). The share is the node-engine's own config as the node's layers give it; each step divides it by its own module's capacity. A share out of range bounds builds at the default and never refuses the node's composition. A change of the share recomposes the build runtimes, which restart once.	2026-10-26 14:42:20 +01:00
jschoubben	852ba81c5a	Build seats yield to one shared slice per node; the composer half waits for the engines (ADR 0553, issue 1806) ... Review round 1: the decoder type ships before any composer can emit it, so a routine SDK bump never sends yields to an engine that refuses them; the composer half moves to a later change. Every yielding process of a node goes into one top-level slice, meshyield.slice, so the three build modules share one quota instead of taking one each; the share is one node value, node-tools' build-cpu-share, and each step's threads divide it by every build slot of the node (words from the composer, a conservative fallback without them).	2026-10-26 14:20:05 +01:00
jschoubben	04902ff24a	Build seats yield: idle priority and a per-node processor cap on their runtimes, threads per step within it (issue 1806) ... The operator's desktop slows while it builds: the Go build runtime took 1650% of shanks' 24 processors with nothing holding it back. A build seat's holder now runs its runtime at idle priority under its node's cpu-cap share (declaration Yields, composed from Seat.Yields and the module's cpu-cap setting), and buildcpu/buildstep give each step its part of that cap in threads.	2026-10-26 13:37:00 +01:00
mesh-tools	5e4fcc6db7	Copy mesh-controller's catalogue into mesh-sdk, part 1: the package and its testdata, from mesh-control 6c2a8d62 (issue 1354)	2026-10-20 06:05:52 +00:00