docs(plans): Telegram C1 across pods is unwalked, not limited by design - #1930
Merged
Merged
Conversation
The merged walk record (#1927) said one Telegram account links one pod "by design". Wren ruled TASK-154 the other way, and the code agrees on the installable path: one private chat holds one active user-scoped row, outbound relays from every pod whose gate is on (config.gates, eventHandlers.ts:59), and inbound goes to the one active pod the owner moves. The walk only hit Sam's pre-installable Aug-27 row. Records both halves with their code locations, and cites D17 (ruled) rather than D8 (Proposed). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MCF2UK3EQ6z6EHdvxAkM44
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.
The walk record merged in #1927 says Telegram C1 is "limited by design": one account links one pod. Wren ruled TASK-154 the other way. On the installable path the code agrees with the ruling, so this corrects both cells: the summary row and the walk section.
What the code does (on
0368d773):routes/webhooks/telegram.ts:135-148). One private chat holds one active Telegram row, because everything typed there is authored as its owner. This stays.activeHandlersForPodselectsscope: 'user'rows withconfig.gates.<podId>.enabled(services/installable/eventHandlers.ts:59). That is N pods behind one chat.podId. The owner moves it with the owner-only PATCH that also writes the gates (routes/integrations.ts, "a movable personal inbound destination"; pod-scoped rows get 400).installationId(it predates feat(connectors): project Telegram as an installable app #1527), so it stays pod-scoped.Why "not walked" and not red: no multi-pod refusal has been observed on an installable row. The single active inbound pod, and quote-replies routing across pods, are TASK-156.
Citation: the pod-gate list is the connector surface from ADR-025 D17 (ruled). The cells say D8 is still Proposed rather than cite it as settled.
Docs only, one file, +2/−2.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MCF2UK3EQ6z6EHdvxAkM44