7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	36061b5c56	Start commands in a directory that exists, and decline an ask whose toolchain could not be read (issue 734) ... A build module runs in the directory its build was unpacked in. When the node-engine replaced that build, every command the module started inherited a deleted working directory, and the toolchain probe's failure became a final refusal of the check that asked it (three checks on ace on 2026-10-26). forgekey: ExecRunnerClean starts its command in the HOME it is given, or the temporary directory; the other runners keep the process's directory while it exists and use the temporary directory once it is gone. buildstep: a guard whose probe failed answers a Refusal with Again set; the puller declines such an ask (delivery.StepDeclined) so its asker puts it again for another node or a later pull, instead of ending it refused. A version mismatch stays a refusal.	2026-10-26 15:01:57 +01:00
jschoubben	92fdc8c86a	Parse the beside catalogue once per test binary, so mesh-sdk's unit level fits its bound (issue 1756)	2026-10-21 19:26:30 +02:00
mesh-tools	1572e50e0e	Give a build step's commands only the environment its caller names (issue 1497)	2026-10-20 20:39:45 +00:00
mesh-tools	0b990a9c31	Name the step's deadline, not a bound never set, when an unbounded command is cut (issue 1497)	2026-10-20 20:09:32 +00:00
mesh-tools	9e296295c0	Let a long step's exec runner be bound by its context alone (issue 1497), part 8 of 8	2026-10-20 20:07:15 +00:00
mesh-tools	a51dc144a1	Test the key keeper (issue 1469), part 2 of 6	2026-10-20 20:04:27 +00:00
mesh-tools	c5705ed551	Move the key keeper into mesh-sdk and add the build modules' shared steps (issues 1469, 1470, 1471, 1473, 1474, 1479), part 1 of 4	2026-10-20 20:03:17 +00:00