fix: shorten telegram switch callbacks#195
Merged
Merged
Conversation
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.
Summary
/lsinline-keyboard callback payloads with deterministic shortsw:<token>values derived from agent ids.relative_agent_listfor the current Telegram agent before switching.Root Cause
Telegram limits
callback_datato 64 bytes. The previous/lsbuttons usedswitch:<full-agent-id>, so long project/task agent IDs were truncated before the callback handler saw them, causing valid agents to be rejected as unknown.Scope
Kept target parsing, inbox layout, send-message routing, voice routing, and reply-tag routing unchanged.
Verification
cargo fmt --checkcargo testcargo clippy --all-targets -- -D warningstelegram-agent-routingapproved commitf978bb2before PR creation.