5 Commits

Include renames

Author	SHA1	Message	Date
jochen	8dfc19c9f7	A silence is said on the shown message, which then times out (issue 373) ... Seen at 14:40: machine.shanks.units was silenced for 7 days with a reason, and its critical popup stood on the desk as "Still open" while the router logged nothing. A silence now edits the message where it is shown to "Silenced until <day>: <headline>" with the reason, no answers and no urgency, so the desk's popup times out; nothing more is said while it lasts. When the silence ends and the condition is still open, the message is edited back to its open words. Resolved while silenced, it is said only where an edit notifies nobody. The silence is taken from the controller's event and from the 10-min reading of the open set alike.	2026-10-10 14:32:35 +02:00
jochen	c2c75ceb3b	Make the messenger the router: it holds every ask, judges each answer and issues the warrant its asker acts on, and keeps no channel's client (hq ADR 0259)	2026-10-09 17:08:17 +02:00
jochen	a6296dfd6f	Say each notification in plain words the operator reads at a glance ... The desktop popups were walls of plan ids, commits, keys and verb syntax in UTC. The messenger now shows the condition's headline, explanation and resolved line, since when in the operator's time zone, and a clearance in one line (hq ADR 0253).	2026-10-08 13:26:26 +02: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