messenger, telegram: show the operator at once what a tap did, and change the question to its outcome (hq issue 372)

At 13:30 on 2026-10-10 the operator approved two questions on Telegram and saw
nothing happen: the channel acknowledged each tap with no words, before the
router had judged it, and the edit that removed the buttons kept the question's
title, adding only a line under it that rings nothing.

The router now answers a chosen option in reply to the tap, once the ask's end
is recorded and before the question is edited: "You chose Approve: recorded,
and claude-code was told." (or, when the bus did not take the warrant, that it
is told when it does). A refusal already replied with its reason. Telegram
holds a tap's acknowledgement for the router's word and shows it as the tap's
own toast; a word with a body (a refusal's reason, Details) also stays in the
chat. Without a word in 8 seconds the toast claims nothing, and the late word
goes to the chat. A secret is never a toast.

An ask's own message, once answered, carries its outcome as its title:
"You chose Approve at 13:30 on Telegram · <headline>", then whether the asker
was told. The asks protocol carries no result back from the asker, so nothing
more is claimed of what it did.

modules/telegram/README.md

@@ -11,6 +11,13 @@ as the operator.
 - **Says what the operator chose** on `intake` under its own kind: a tapped button (`choice`), with the
   sender as Telegram authenticated it; `/start` (`link`); a message it could not deliver (`failed`); and
   whether it can send (`standing`). Only a private chat with the account itself counts.
+- **A tap is acknowledged on the phone with the router's word on it** (issue 372): the router answers a
+  choice with a message in reply to it — "You chose Approve: recorded, and claude-code was told.", or why it
+  was not taken — and this channel shows that as the tap's own acknowledgement, the short line Telegram
+  shows over the chat. A word with more to it (a refusal's reason, Details) is also said in the chat, where it
+  stays. Nothing is acknowledged before the router's word, so the phone never says "recorded" for what was
+  not; without a word in 8 seconds the tap is acknowledged with words that claim nothing, and the word when it
+  comes is said in the chat. A secret is never an acknowledgement.
 - **A code** (six digits, the one shown on the desk when linking) is asked of the router as a proof, by
   request and reply: never in an event, never kept, and deleted from the chat at once.
 - **Judges nothing.** Whether the sender is the operator, and what an answer may do, is the router's.