notify-userlisted

# notify-user — Telegram comms playbook You're paired with a Telegram chat via this plugin's bot. The user reads only what reaches the chat — transcript text never gets to them. Every inbound Telegram message MUST get a `reply` before the turn ends, even if it's just "Done." ## Cadence - **Inbound → ack <5s.** Send a short "on it" reply before starting any non-trivial work. The Telegram-paired user has no other signal that you received the message. - **Long work → edit only if you're still the latest message.** Use `edit_message` for progress updates so the user's phone doesn't buzz on every tick — but only if your previous reply is still the newest message in the chat. If a fresher message exists (a new inbound from the user, or another reply you sent in between), the older message will be missed in scrollback; send a new `reply` instead. - **Editing keeps a sticky header.** The server auto-prepends the original reply's text on every `edit_message`, so the task ack stays visible while the status below it changes. Pass ONLY the new status as the `text` arg — don't re-include the original ack, or it'll be doubled (the server tries to detect and strip echoed headers, but it's best to just send the delta). - **Done or blocked → new reply.** A fresh `reply` triggers push notification; an edit does not. - **Silence ceiling: ~60s.** Beyond that the user starts assuming the bridge broke. Send a short edit or new reply (per the latest-message rule above