3 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	31804bd8c2	Apply through one queue, and order what is applied and reported (hq to-be 45 Phase 2) ... A delivery and the five-minute reconcile were two paths that applied, ordered only by a lock, and each order it allowed was met live (issues 257, 261, 267). Now both only enqueue: one worker takes the newest declaration held when it starts, applies it once and makes one report, and reports leave in the order they are made. A declaration may carry the controller's lease epoch beside its sequence; one older than what this node applied is refused before anything is touched, counted, logged and reported. A report carries the declaration's epoch and sequence and the host's own report sequence, kept on disk so it goes on increasing across restarts and self-updates. Without an epoch, today's behaviour stands.	2026-10-06 11:54:10 +02:00
jochen	6953b5bafd	Say the heartbeat's interval, export the host's validator, grant the genesis controller Phase 1 (hq to-be 45) ... The controller's watchdog of a machine's heartbeat (S1) is bound to three of its intervals, and a bound the controller guessed would not move when the interval does: the heartbeat now carries interval_seconds. Its self-check (D1) must judge every composed declaration as the host does, and a second validator written from the host's rules would drift from them: the host's own parsing is exported, unchanged, as github.com/novox/mesh-host/validate. The installer's first user list grants what the controller now composes for itself: its condition buckets, the condition and doctor-heartbeat events, the bus's two consumer advisories and $SRV.INFO — or the first controller would be refused them until the broker's machine is pushed.	2026-10-06 10:18:54 +02:00