Add a getWebhookInfo verification step to the Telegram doc

setWebhook returning ok:true only means Telegram accepted the
request, not that the secret_token it was given actually matches
TELEGRAM_WEBHOOK_SECRET on the Worker -- those are two independent
systems with nothing cross-checking them. A mismatch there fails
silently: setWebhook still reports success, the bot just never
replies to anything, and nothing about that state is visible without
checking getWebhookInfo's last_error_message specifically.
nccommitted parent 0b9efb9cbba15ee66253577c8dca98f92430f1fb1d70834Browse files
1 file changed+8−0

Rendering diff…