fix: preserve Telegram topic inheritance history#91
Merged
Conversation
- what: store historical future-thread defaults by topic/thread boundary, wire the fallback into Telegram session seeding, and tighten the Telegram E2E probe/docs - why: older untouched forum topics were inheriting the newest parent model/thinking when Telegram missed topic-create seeding, which made live behavior inconsistent - risk: future-thread defaults now carry extra session metadata, so Telegram thread inheritance and probe assumptions are the main regression surface
artemgetmann
force-pushed
the
codex/chat-worktree-20260323-1651
branch
from
37ae7c7 to
30c746d
Compare
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
Why
Telegram forum topic creation is not reliable enough to be the only snapshot path. Without a fallback, an older untouched topic can inherit the newest parent default the first time it is used, which is wrong.
Verification
pnpm test -- src/sessions/future-thread-defaults.test.tspnpm test -- src/auto-reply/reply/session.test.ts -t "historical parent defaults|native target session routing|forum topic sessions"pnpm test -- extensions/telegram/src/thread-session-seeding.test.tspnpm buildanthropic/claude-sonnet-4-6+adaptive