4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	21c86c819c	Follow the runtime's watches through mesh-sdk's KeptState.Follow, not four loops of their own (issue 774) ... mesh-provisioner, mesh-config, mesh-issues and mesh-healers each wrote a watch-again loop (`watched`). mesh-sdk 61b67d61 adds KeptState.Follow, which asks again with backoff and says each give-up, and its watches now answer a change at once and run the handler beside the runtime (the provisioner's "names no watch of this bundle"). The four modules use it; their loops are gone. Built and tested against the mesh-sdk group head through a go.work that is not committed: their mesh-sdk pins move to that head with the group.	2026-10-30 18:33:32 +01:00
jschoubben	6d67c22bf3	One bad module must not drop its node: the provisioner composes each module's plan on its own (issue 774) ... novox since 15:36 (nats's built manifest) and ace since 15:37 (baserow's config.json) had no plans at all, so the vault refused every secret their clients asked. The holder now composes with frombus.PlansHeld: a module whose build or plan refuses is held, its why kept in the new state refused and read by provisioner_plans, its last plan and its provisions left as they were, and every other module on the node composed and written. Pins mesh-sdk 59311407.	2026-10-30 17:55:19 +01:00
jschoubben	35ff67bda0	Design 47's last milestones: the keeper, self-check, healers, hand-acts, provisioner, vault, artifact sweep, disk readings, credential forms (issues 774, 1952, 1953, 1954, 1955) ... One commit with exactly the tree of the reviewed head 35b4509c0a, on main 12c2574c9d, so two compiled programs added and removed on the branch leave no trace in history (issue 1577).	2026-10-30 02:21:51 +01:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00