claude
45231ba69e
getUpdates, sendMessage, answerCallbackQuery and editMessageReplyMarkup, plus the inbound shapes cut to what the poller reads. Every error goes through the sink's redaction: the token is in the URL path because telegram accepts it nowhere else, and net/http prints that URL on a transport failure. Only ok=true is a success, the same rule the push half already applies. A relay that is up but cannot reach api.telegram.org answers 200 with an HTML page of its own, and reading that as a batch of updates would be silent. A chat id arrives as a number for a user and a string for a channel, so it is held as json.Number and never converted.