fix(msteams): include sessionKey in canonical hook context

ndholakia · ndholakia · commit 419da85f07c6 · 2026-05-15T21:48:15.000-05:00
Addresses ClawSweeper review finding [P2] on PR #82354. Pass `params.sessionKeyForInternalHooks` as the `sessionKey` field of the canonical hook context built in `buildMSTeamsSentHookContext`, not just as the internal-hook routing key. Telegram's `buildTelegramSentHookContext` does not include sessionKey either — but the canonical context type accepts it, and the plugin-SDK consumers reading the canonical/plugin context object (via `toPluginMessageContext`) can use it to correlate the sent event with the originating agent session. Including it costs nothing.
diff --git a/extensions/msteams/src/delivery-hooks.ts b/extensions/msteams/src/delivery-hooks.ts
@@ -69,6 +69,11 @@ function buildMSTeamsSentHookContext(params: EmitMSTeamsMessageSentHookParams) {
     channelId: "msteams",
     accountId: params.accountId,
     conversationId: params.conversationId ?? params.to,
+    // Include the session key in the canonical hook context (not just as the
+    // internal-hook routing key) so plugin-SDK consumers reading the
+    // canonical/plugin context object can correlate the sent event with
+    // the originating agent session.
+    sessionKey: params.sessionKeyForInternalHooks,
     messageId: params.messageId,
     isGroup: params.isGroup,
     groupId: params.groupId,
