#7224: feat(telegram): inherit forum topic bindings from parent group

## Summary When a Telegram forum topic message doesn't match a direct peer binding, now checks if the parent group has a binding and uses that agent. This enables multi-agent setups where forum topics inherit their parent group's agent binding automatically, consistent with Discord thread behavior added in #3892. ## Problem In Telegram forum groups with topics enabled, messages have a peer ID like `-1003726751869:topic:42`. If you configure a binding for the group ID `-1003726751869`, topics don't inherit that binding and fall back to the default agent. ## Solution Pass `parentPeer` (the group ID without `:topic:N` suffix) to `resolveAgentRoute` for forum topic messages, similar to how Discord threads pass their parent channel. ## Changes - `src/telegram/bot-message-context.ts`: Pass parentPeer for forum topics - `src/telegram/bot.ts`: Pass parentPeer in reaction handler for forum topics - `src/telegram/bot-native-commands.ts`: Pass parentPeer for native commands in forum topics - `src/routing/resolve-route.test.ts`: Add tests for Telegram forum topic binding inheritance - `CHANGELOG.md`: Add changelog entry ## Testing - Added 3 new tests for Telegram forum topic binding inheritance - All existing tests pass - Manually tested with a Telegram forum group ## Related - #3892 - Discord thread parent binding inheritance (same pattern) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates Telegram routing so forum topic messages (which have peer IDs like `-100...:topic:N`) can inherit agent bindings from their parent group when there is no direct topic binding. It does this by passing a `parentPeer` (the base group peer) into `resolveAgentRoute` from three Telegram entry points: message context building, reaction handling, and native commands. It also adds routing tests covering Telegram forum topic inheritance and records the change in the changelog. This aligns Telegram forum topic behavior with the existing `parentPeer` inheritance mechanism used for Discord threads in `src/routing/resolve-route.ts`. <h3>Confidence Score: 3/5</h3> - This PR is likely safe to merge, but there is at least one concrete test/type issue to fix before it will pass CI reliably. - Runtime logic change is small and uses an existing routing feature (`parentPeer`) consistently across Telegram handlers, but the new/modified tests appear to use an incorrect config type name (`MoltbotConfig`) that can break type-checking. - src/routing/resolve-route.test.ts; CHANGELOG.md <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->