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	4e9621edd6	Lead a refusal of a held module's stand-in with why the module was held, so its first reason is never hidden (issue 774) ... The proposal on ace said only "mesh-self-check runs as its own account and declares no own secret broker": the words of its bare stub, held for "has no bus credential", which no one saw. The second hidden first reason of the day, after "0 bundle(s)". Quick fix: log the held map in composeEach. Thorough fix: firstReason leads a refusal no culprit is found for with the first reason of every held module it names ("<m> is held: <why>; its stand-in is then refused: <err>"), for Compose and the node's Answer alike; the hold's own why already keeps its first words. Chose thorough.	2026-10-30 20:33:54 +01:00
jschoubben	9685990a15	Compose a module at the build its want names and hold a running one whose build is not done, so the runtime never loses its bundle (issue 774) ... At 19:30 on 2026-10-30 node-tools' trunk fingerprint moved to a build not yet done; fromBuilds then composed it from the indexer's manifest, which names no bundle, and ace, g14 and shanks refused every module ("its build produced 0 bundle(s)") until another input moved after the build landed. Quick fix: skip the runtime's check while its build is not done. Thorough fix: Compose reads each placed module at the build its want names (as Scope.KeptAt), and a module that runs whose build is not done is held, keeping what runs (a held runtime is composed as what runs of it, its running bundle), named with why; a module nothing runs of still composes from the indexer's manifest as before. Input, PlansHeld and Answer read the trunk's builds as before. Chose thorough: no running module is ever composed from a source manifest that names no build.	2026-10-30 19:45:32 +01:00
jschoubben	d539d7e4eb	Take the runtime as a culprit only where its stub composes, so node-tools is never held for an error that names it (issue 774) ... The culprit rule held a module whose stub made the composition fail otherwise. The runtime's stub carries no bundle, so it always fails otherwise: any refusal naming node-tools (or a module whose name holds it) held the runtime, and the node was then refused whole for the runtime's "0 bundle(s)". Quick fix: never take node-tools as a culprit. Thorough fix: blames, the rule as one function, takes the runtime only where its stub composes. Chose thorough: a runtime whose stub composes may still be held alone.	2026-10-30 19:44:08 +01:00
jschoubben	c1bc21c35f	Say what a node held on the way when it is refused whole, so a held module's own refusal is never hidden (issue 774) ... At 19:30 on 2026-10-30 ace, g14 and shanks refused every module with "node-tools … its build produced 0 bundle(s)": the refusal of node-tools' stand-in, while why node-tools could not be composed was dropped with the hold. Quick fix: log held in mesh-host before marking. Thorough fix: Compose's node-wide error carries "(held before: <module>: <why>; …)", so the engine's journal, every have's detail and any caller see the cause. Chose thorough.	2026-10-30 19:43:46 +01:00