4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	66650e315c	Take a registered module's new done key in, compose it and grant it; at start delete the plans' buckets and compose every node and the replaced controller (issue 1945, B3, B5, B13) ... With no plan left to take a done key in, a write of the builder's keys registers the new fingerprint, composes the module's nodes and the bus's user list, and writes its grant, so the assigner's rules can name it (ADR 0539 clauses 5 and 7). The new controller composes every node at its start, and the controller it replaced at its own fingerprint, the operator's way back (clause 10); the merge window's, silent sends' and building plans' buckets are no longer asserted and are deleted once, each said as the event bucket-deleted (clause 13). The assigner may read the compositions' digests, and a node-engine hears its backup holder's backed-up.	2026-10-24 17:11:01 +02:00
jschoubben	14fe2ad736	Split the unit level from the integration level outside cmd, builder, link, catalogue, inventory; merge-check.sh times and bounds the unit level (issue 895)	2026-10-17 20:41:57 +02:00
mesh-tools	d984816844	Feature 57 (config and provisioning): release mesh-controller, the reviewed release branch merged with main, on top of main	2026-10-16 08:28:38 +00:00
jochen	7bd61332cb	Let a module declare a log the controller creates and never removes (ADR 0297) ... The issue tracker's history lasts seven days on the events stream and its bucket fills toward a cap with no warning (issues 501, 502). A module may now declare `logs`; the controller creates each as a stream on the bus (create-or-update, never deleted or recreated, reported when undeclared), issues it to the owner's assignments in their membership, grants the runtime exactly the append and direct-read subjects, and raises a condition when any module's bucket or log reaches 75% of its cap, cleared below 70%.	2026-10-11 19:22:43 +02:00