Run live Telegram smoke for ccbot send_bot_message

[iqdoctor]

Follow-up from reviewed send_bot_message hardening on feat/multi-runtime-topic-control.

Known gap:

• Unit tests cover explicit chat/thread, state-derived document/photo delivery, missing-token errors, and fail-closed topic routing.
• Not yet live-smoked against a production bot token/chat after the safety hardening.

Suggested check:

1. Use a safe test chat/topic bound to ccbot.
2. Send a small text payload via ccbot send_bot_message --chat-id <chat> --message "smoke".
3. Send a small file payload via ccbot send_bot_message --chat-id <chat> --file-path <tmp-file> --file-kind document.
4. Confirm both land in the expected Telegram surface and no fallback/private-topic leak occurs.

Verification already run before filing:

• uv run --extra dev pytest -q -> 713 passed
• uv run --extra dev ruff check src/ccbot tests/ccbot -> passed
• uv run --extra dev pyright src/ccbot/send_bot_message.py tests/ccbot/test_send_bot_message.py -> 0 errors
• desloppify scan --path . -> strict 79.0 / objective 88.4, queue 0 via desloppify next