Set up Telegram bot on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/telegram-bot.md?via=terminal from top to bottom. The recipe's example VM name is my-telegram-bot. This VM's name is the output of `hostname`: use it wherever the recipe writes my-telegram-bot. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - `telegram-bot.service`, restarted on failure and reboot, long-polling Telegram through the integration and logging `connected to Telegram as @`. - Claude answering in private chats, and when mentioned or replied to in groups, with each chat's last 20 messages remembered in SQLite. - Photos, PDFs, and text files sent to the bot downloaded through the integration's `/file/` path and read by the model. - The bot token held by exe.dev's Telegram integration and models from the LLM integration, with neither secret on the VM. - The bot claimed by its owner through a one-time link, and ignoring everyone they haven't invited. Read the whole recipe, closed details included, and follow "Set up by hand" in order, skipping VM creation; the walkthrough above it is for the owner. The bot token must never be on this VM: don't ask for it. First give the owner the steps in "Make a bot" and "Give exe.dev the token", with the connect link for this VM's name, and install the bot while they do that; the service retries until the integration is attached. If `curl -s https://reflection.int.exe.xyz/integrations` shows their Telegram integration under a name other than `telegram`, set TELEGRAM_API in ~/telegram-bot/bot.env to match. When the log shows the owner link, give it to the owner. Stay with long polling unless they ask for webhooks. End with the owner link, what to try, and how to change the prompt. Finish with the URLs I should open.