fix(telegram): use context cfg in route resolution, fix topic-agentid test harness

Groos-dev · Groos-dev · commit 8365268495b7 · 2026-03-16T08:48:09.000+08:00
diff --git a/src/telegram/bot-message-context.topic-agentid.test.ts b/src/telegram/bot-message-context.topic-agentid.test.ts
@@ -43,6 +43,7 @@ describe("buildTelegramMessageContext per-topic agentId routing", () => {
   }) {
     return await buildTelegramMessageContextForTest({
       message: buildForumMessage(params.threadId),
+      cfg: loadConfig() as never,
       options: { forceWasMentioned: true },
       resolveGroupActivation: () => true,
       resolveTelegramGroupConfig: () => ({
@@ -115,6 +116,7 @@ describe("buildTelegramMessageContext per-topic agentId routing", () => {
 
   it("routes DM topic to specific agent when agentId is set", async () => {
     const ctx = await buildTelegramMessageContextForTest({
+      cfg: loadConfig() as never,
       message: {
         message_id: 1,
         chat: {
diff --git a/src/telegram/bot-message-context.ts b/src/telegram/bot-message-context.ts
@@ -82,7 +82,7 @@ export const buildTelegramMessageContext = async ({
   // Fresh config for bindings lookup; other routing inputs are payload-derived.
   const freshCfg = loadConfig();
   let { route, configuredBinding, configuredBindingSessionKey } = resolveTelegramConversationRoute({
-    cfg: freshCfg,
+    cfg,
     accountId: account.accountId,
     chatId,
     isGroup,
