-
Notifications
You must be signed in to change notification settings - Fork 12.9k
docs(add-telegram): match pairing status-block names to the setup step; fix adapter pin#2729
Open
sturdy4days wants to merge 1 commit into
Open
docs(add-telegram): match pairing status-block names to the setup step; fix adapter pin #2729sturdy4days wants to merge 1 commit into
sturdy4days wants to merge 1 commit into
Conversation
...p; fix adapter pin The pairing walkthrough referenced status blocks the pair-telegram setup step never emits: PAIR_TELEGRAM_ISSUED, REMINDER_TO_ASSISTANT, PAIR_TELEGRAM_NEW_CODE, RECEIVED_CODE, and ADMIN_USER_ID. The step actually emits PAIR_TELEGRAM_CODE (REASON=initial|regenerated), PAIR_TELEGRAM_ATTEMPT (CANDIDATE), and a final PAIR_TELEGRAM with PAIRED_USER_ID (setup/pair-telegram.ts). An assistant following the doc waits for blocks that never arrive. Also pin @chat-adapter/telegram at 4.26.0 to match the channels branch: installing 4.27.0 against the resolved chat core produces ChatInstance type-mismatch build errors in createChatSdkBridge, and step 6 fails. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
What
Two corrections to
.claude/skills/add-telegram/SKILL.md, both found by following the skill end-to-end:1. The pairing walkthrough references status blocks the setup step never emits. The doc says to watch for
PAIR_TELEGRAM_ISSUED(with aREMINDER_TO_ASSISTANTline),RECEIVED_CODEon attempts,PAIR_TELEGRAM_NEW_CODEon regeneration, andADMIN_USER_IDon success.setup/pair-telegram.tsactually emits:PAIR_TELEGRAM_CODE{ CODE, REASON=initial|regenerated }PAIR_TELEGRAM_ATTEMPT{ CANDIDATE }PAIR_TELEGRAM(final){ STATUS, CODE, INTENT, PLATFORM_ID, IS_GROUP, PAIRED_USER_ID }An assistant following the doc literally waits for blocks that never arrive. Updated the walkthrough to the real names.
2. The adapter pin conflicts with the channels branch. The doc says
pnpm install @chat-adapter/telegram@4.27.0, but thechannelsbranch pins4.26.0. Installing 4.27.0 against the resolvedchatcore producesChatInstancetype-mismatch errors increateChatSdkBridge, so step 6 (pnpm run build) fails. Pinned the doc to 4.26.0 and added a sentence explaining the pin must track the channels branch.Doc-only change; no code touched.
🤖 Generated with Claude Code