11 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c1eb7783e8	Pin the newest mesh-sdk in the modules of the leaves (issue 1955)	2026-10-30 00:02:39 +01:00
jschoubben	3d3524dd69	mesh-watcher: read who holds the controller and the bus from the placement seat's state, not the controller's seats (issue 1955, ADR 0571 clause 4)	2026-10-29 23:46:55 +01:00
jschoubben	1f0ff6ed98	Every offer of twenty providers says its credential form; a check refuses one that does not; re-pin sdk 6b8c694 (issue 1952)	2026-10-29 22:49:41 +01:00
jschoubben	8fac0f89f7	Re-pin the release sdk; the nats tools' secret directory is /var/lib/mesh/nats-tools (issue 1952)	2026-10-29 22:01:47 +01:00
jschoubben	9ccb6f4060	Re-pin the release sdk; the nats tools' credential gets a directory of its own the tools can reach (issue 1952)	2026-10-29 22:00:20 +01:00
jschoubben	2669fc29d8	Re-pin the release sdk; the bus module's tools declare the two removals they hold and leave the credential to the runtime (issue 1952 N1-N3)	2026-10-29 21:54:42 +01:00
jschoubben	77f6b4292c	mesh-watcher: hear the self-check run the take-over key names; take the release sdk and go 1.26 (issue 1952 W1)	2026-10-29 21:46:15 +01:00
mesh-tools	652b00b25b	Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422) ... Every directory and archive resource carries `unknown`: move-out for a home folder whose program writes nothing there (the node-engine, delivered in mesh-host #117, moves the rest to ~/.local/state/mesh-moved/<module>/ with a list), module for ~/.ssh and ~/.claude, program elsewhere; `knows` keeps what a program or the operator relies on (powerlevel10k's compiled files, i3's scripts and the asus/g14 drop-ins, dunst's slack rule, betterbird's records, node-env's forge credential, issue 1033). Two shared folders are no longer declared. Each module's README says it. checks/owned holds every manifest to it; checks/sshdir stays while main's merge check runs it (issue 1035). Tests that pin a manifest follow the new key only. Reviewed in three rounds.	2026-10-17 16:23:03 +00: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
jochen	a4b92c1306	messenger: never say history as news — read the open conditions first, coalesce bursts ... A consumer made on 2026-10-06 was handed three hours of raised-and-cleared conditions at once and the holder said each as new: 20 desktop notifications in a second. What is said is now decided by the controller's open set and by an event's own time, never by its arrival; bursts are one message, the desktop gets warnings at most every 15 min, the cap is said once, and the first minute after start says only the urgent conditions still open. Replays of that morning's 96 events are tests. Also drops two committed binaries. (novox/hq issue 271)	2026-10-06 12:03:19 +02:00
jochen	0ae7933d54	Tell the operator what the mesh finds wrong, and watch the watcher (hq to-be 45 phase 1) ... The mesh noticed 48 core failures in six days and told nobody (ADR 0227). messenger holds the operator-channel seat: it consumes the controller's condition events and sends them to Telegram and the desktop notifier, deduplicated by key, reminded once, edited on clear, capped at 20 an hour with the rest folded, and refusing anything carrying an address, a path or a secret. mesh-watcher, on a machine other than the control node, sends to Telegram directly when the self-check heartbeat or the bus goes silent.	2026-10-06 09:35:55 +02:00