4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	b9c24a7b42	Read the vault's structured move-in refusal and take a value it holds another of as superseded, so the move is not asked again for ever (issue 774) ... mesh-vault (mesh-catalog f3b13de2) answers a move it refuses with `refused: {reason, held}` and `why`, and no read-back. The engine read only the read-back, so every such row failed "answered with no read-back" and the controller asked it again on every pass. Quick fix: treat any answer without a read-back as done. Thorough fix (chosen): read `refused`. For holds-another-value the vault's value is the live one: the move answers done, superseded, at the held generation with the held record in its words, so the controller records the row and stops asking; the journal says it once per secret. Any other reason fails in the vault's own words.	2026-10-30 18:36:38 +01:00
jschoubben	b2003e7a38	A composition is applied only when the controller or the operator signed it; the node agent's integration tests on an embedded bus (R6-A A9, A1, A5)	2026-10-24 16:42:11 +02:00
jschoubben	1598156752	The node-engine hears no declaration: the queue, orders, put-backs, unsaid, numbers and news go; a session says the facts in the node-engine's own order, and the first have proves a build (R6-A A7, A8)	2026-10-24 16:25:11 +02:00
mesh-tools	bff1ac14a1	Feature 57 (config and provisioning): release mesh-host, the reviewed release branch on top of main	2026-10-16 08:24:13 +00:00