Settings › Telegram: polish seen while testing the webhook

Seen while rendering Settings › Integrations › Telegram at 1440px and 375px (Task 7164). 1. While the Bot credential list loads, the Bot select shows a raw id ("Credential 1e5eaaea-33b6-4e…"). Show "Loading…" or the name, as other pointer knobs do, and never the id. 2. The webhook panel can sit on "Loading…" for 10+ seconds when Telegram is slow, with no timeout and no hint. Put a short timeout on the read in the API, and show what is being waited on ("Asking Telegram…"). 3. "Telegram did not answer (Unauthorized)" is wrong: Telegram did answer, and refused the token. Word a 4xx refusal as "Telegram refused the bot token (Unauthorized)" and keep "did not answer" for a network failure. 4. At 375px, "Clear" sits alone on a row under the Bot select. Put it on the select's row, or tighten the space, so the card does not grow. Out of scope: delivery behaviour, plan gating, the events vocabulary. Done means: - Each item shipped, or rejected with a reason in the PR body. - Settings › Integrations › Telegram rendered at 1440px and 375px, with screenshots in the report. - `./dc check full` green.

All 4 Telegram polish items shipped (no raw id, 4s webhook read + "Asking Telegram…", refused-vs-no-answer wording, Clear inline at 375px); full gate green in lane, merged c1484bb6b; visual check done at 1440/375. Follow-up draft 7224.