4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	150fadfe8b	Write a removal after a restart from the declaration the apply replaced (issue 1369) ... The set of modules this process wrote lives in memory, so a node-engine restarted before the apply that drops a module never wrote that module's removal. The report now names the modules the kept declaration held before, and they are removal candidates.	2026-10-20 01:26:33 +00:00
mesh-tools	6a2fb63bfc	Write a module's have key as removed when the applied declaration no longer holds it (issue 1369) ... A module that left a node kept its have key at running for ever, so nothing could tell it stopped and the gate would never take the seat. The key is written once with the phase removed over the revision read, never deleted. Pins mesh-sdk to the commit that adds the phase.	2026-10-20 01:20:52 +00:00
jschoubben	9d9e3a46c4	Bind the have bucket once per pass, bound by the queue's timeout, and stop the pass at the first error (issue 1132)	2026-10-18 19:18:08 +02:00
jschoubben	0b391f49a2	Write each module's have and the node's own facts beside the report, grouped per module and keyed by the module the controller names (issue 1132) ... The node-engine reads a resource's module and a declaration's builds, says it does in every report (reads_modules), groups the apply's outcome per module with every failing resource named, and writes have.<node>.<module> and have.<node>.node to the bucket only when a value differs, never ahead of or in place of the report (novox/hq ADR 0429 section 4).	2026-10-18 19:10:05 +02:00