Telegram round-trip prep: verified setup path and founder runbook - #27
Open
nishantkluhera wants to merge 1 commit into
Open
Telegram round-trip prep: verified setup path and founder runbook#27nishantkluhera wants to merge 1 commit into
nishantkluhera wants to merge 1 commit into
Conversation
Static verification with receipts: the native telegram platform plugin byte-compiles clean, requires exactly TELEGRAM_BOT_TOKEN, auto-connects once enabled+token resolve (gateway/config.py:629, 1031-1043), and its python-telegram-bot[webhooks]==22.8 dep is pinned in pyproject. Runbook covers the founder-side steps (BotFather, allowlist via user ID, .env template, gateway launch, /status + plain-message probes) and the gaps found: no LLM provider config exists on this machine yet, and TELEGRAM_HOME_CHANNEL should be set after first successful DM. Live test intentionally left to the founder - the bot token can only be minted from their Telegram account. Refs #6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Static verification with receipts: the native telegram platform plugin byte-compiles clean, requires exactly TELEGRAM_BOT_TOKEN, auto-connects once enabled+token resolve (gateway/config.py:629, 1031-1043), dep pinned in pyproject.
Runbook covers the founder-side steps (BotFather, allowlist via user ID, .env template, gateway launch, /status + plain-message probes). The live round-trip itself is intentionally left for the founder - the bot token can only be minted from their Telegram account. This PR is the prep half of #6; do not close the issue until a real message round-trips.
Prep for #6
Merge order: #26 first, then this.