6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	8be1c2ab0d	The node agent writes what the machine observes of itself as its record in its own have key, only when it changed (issue 1126, ADR 0555 §3)	2026-10-26 18:32:54 +01:00
jschoubben	99285cb080	Retry an apply, a fetch by digest and a have write that met the bus reloading, and keep the cause in the have ... The bus node's engine writes the bus user list (ADR 0547 bridge); each write makes the bus reload its accounts, and for about three seconds every JetStream request meets no responders. An apply that failed then was kept failed until a key changed (mesh-vault on novox, 2026-10-25 23:04:24), holding every module that needs the secret seat. A transient bus failure is now retried with a backoff (2 s, 5 s, 15 s, 60 s, then every 5 min), the have saying retrying meanwhile; after the engine writes the user list, the transiently failed modules are tried again once the reload is over. A have write that met it is written again the same way. shorten keeps the head and the tail, the cause.	2026-10-25 23:37:02 +01:00
jschoubben	b32a27c115	Owe a look when a module's change ends unjudged, so a module with nothing long-running is ok within a look of its apply ... The facts look inside an apply runs while the module is still applying and judges nothing; the running write then left xorg running and unknown until the five-minute statement, holding every x11-display consumer behind it. The running write now nudges the health loop, which looks and says at once. A declaration's report gets the same motion and composition check, and a removed module leaves nothing marked unjudged (review of fix 15).	2026-10-25 15:46:05 +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	3303797bfb	The node agent runs in the node-engine: watches the wants and compositions on the link, applies one module's composition, asks the backup, writes the haves (R6-A A1, A5, A6)	2026-10-24 16:39:51 +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