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

The review found that a double tap while the phone's spinner turned would be
answered 'That answer was not taken', reading as if the approval failed; it is
now 'You already chose Approve at 13:30: recorded.' and does nothing more. The
fallback toast no longer promises a change that may not come (a stranger's
tap), the wait outlasts the router's 10 s wait for the controller's root word,
the channel's own refusals stay in the chat too, and the store's error words
stay in the journal.

modules/telegram/README.md

@@ -16,7 +16,7 @@ as the operator.
   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
+  not; without a word in 13 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.