5 Commits

Include renames

Author	SHA1	Message	Date
jochen	f8515219b1	Review: a blip swallows no escalation or waiting reminder; replace safely (issue 373) ... - A comeback before the clearing was said rings when it is urgent now, and says the reminder or escalation that was waiting when it cleared. - Comebacks never said are counted apart, so "again, Nth time" counts only what the operator was told; an urgent comeback after a said clearing rings again in place of its message. - telegram sends the new message before deleting the earlier one, so a failed send leaves the operator a message. - desk-channel keeps a machine's notification on record when its replace fails, and says a message shown nowhere as failed. - A store that cannot be read sends a new message instead of holding it. - Tests for each, and for a reminder in a burst and a clearing the channel could not take.	2026-10-10 14:22:53 +02:00
jochen	3345ff9317	One message per problem: a reminder replaces, a blip says nothing (issues 373 and 369) ... The operator stopped believing the mesh's notifications: one problem stood twice on the desk (a reminder beside the message it followed, an escalation then a reminder 31 s later), a unit failing again at each apply was said again 22 times, and a question's buttons outlived it on a reminder the ask's end never reached. - messenger: a reminder or escalation is said in place of the problem's message (Replace under its handle), alone, never as a digest line; a problem first said in a digest gets its own message next time. A reminder counts from when it was last said. A clearing is said once it stays cleared 2 min (10 min once it came back); back before that, the message continues without a word. Cleared before ever said and back: said. An ask's expiry is said with its day. - desk-channel: a send or show under a handle already shown replaces its notification by the notifier's replace id. - telegram: the same deletes the earlier message and sends the new one, ringing as its kind rings; one it cannot delete loses its buttons.	2026-10-10 14:22:42 +02:00
jschoubben	0284204989	desk-channel: run as its own account, and show a link's code only where a notifier heard unpaused will show it, kept in no history ... The review of 2026-10-09 (H4). The desk ran in the operator's runtime, where agents run; it now runs as the account desk-channel, as telegram does. A link's code is shown only on a named machine whose notifier said in the last five minutes that it is not paused, and is sent secret, so the notifier keeps it out of the history every caller of the verbs reads; while no such machine exists the desk says it cannot send, and the router starts no link.	2026-10-09 17:08:17 +02:00
jochen	0d9ec84a9c	Run telegram as its own account in a runtime of its own, keep its offset per update, and keep no copy of a secret on the desk (hq ADR 0259 §8)	2026-10-09 17:08:17 +02:00
jochen	a412389725	Add telegram and the desk as channels of their own, each judging nothing and holding only its own secret (hq ADR 0259)	2026-10-09 17:08:17 +02:00