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

..

bot.go

messenger, telegram: a second tap on the recorded answer is said as recorded, and the fallback claims nothing (issue 372 review)

2026-10-10 14:05:41 +02:00

channel_test.go

Review: a blip swallows no escalation or waiting reminder; replace safely (issue 373)

2026-10-10 14:22:53 +02:00

channel.go

Review: a blip swallows no escalation or waiting reminder; replace safely (issue 373)

2026-10-10 14:22:53 +02:00

main.go

telegram: take a tap only on a message showing the words this channel put there, and say where an approval from Telegram means something

2026-10-09 17:08:17 +02:00

manifest_test.go

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