@cuylabs/agent-channel-teams 0.10.0 → 0.12.0

package/README.md

@@ -24,25 +24,42 @@ Teams
 The value is:
 
 - parsed Teams activity metadata instead of raw `activity.channelData`
-- Teams-specific hooks for dialog open/submit, search-style invokes, card submit, feedback, edits, deletes, and reactions
+- curated Teams helpers (`TeamsInfo`, `parseTeamsChannelData`) exposed through the cuylabs package
+- Teams-specific hooks for conversation lifecycle, dialog/task modules, message extensions, tabs, config, card submits, feedback, edits, deletes, reactions, and meeting events
 - Teams response builders for dialog and search-style invoke payloads
 - invoke response helpers for Teams handlers, plus fallback access to generic M365 `onInvoke`
+- attachment download helpers exposed through the curated Teams helper surface
 - ambient Teams turn context that tools and middleware can read
 - a way for Teams-specific handlers to still call back into `agent-core`
 
 ## What It Does Not Do
 
 - it does not replace `agent-channel-m365`
-- it does not require `@microsoft/agents-hosting-extensions-teams`
 - it does not copy Microsoft's routing model
 - it does not turn `agent-core` into a Teams-only framework
 
 ## Install
 
 ```bash
-pnpm add @cuylabs/agent-channel-teams @cuylabs/agent-channel-m365 @microsoft/agents-hosting express
+pnpm add @cuylabs/agent-channel-teams @cuylabs/agent-channel-m365 @microsoft/agents-hosting @microsoft/agents-hosting-extensions-teams express
 ```
 
+`agent-channel-teams` depends on `@microsoft/agents-hosting-extensions-teams`
+because Teams helpers and typed channel data are part of the supported bridge
+contract, not an optional add-on.
+
+## Bridge Design
+
+`agent-channel-teams` is the Teams-native facade for the cuylabs stack:
+
+- `agent-core` still owns the agentic loop, tools, and inference
+- `agent-channel-m365` still owns generic M365 transport and `TurnContext` bridging
+- `agent-channel-teams` adds Teams-specific dispatch, typed metadata, and helper access
+- Microsoft `AgentApplication` routing abstractions are intentionally not the public programming model here
+
+That means you can use Microsoft Teams helpers where they fit, while keeping the
+application architecture centered on cuylabs handlers and `agent-core`.
+
 ## Example
 
 ```ts
@@ -64,9 +81,11 @@ const teams = createTeamsChannelAdapter({
     },
   }),
   handlers: {
-    async dialogSubmit(ctx) {
+    async taskSubmit(ctx) {
       const prompt = JSON.stringify(ctx.turnContext.activity.value);
-      const events = ctx.runAgent(`Handle this Teams dialog payload:\n${prompt}`);
+      const events = ctx.runAgent(
+        `Handle this Teams dialog payload:\n${prompt}`,
+      );
 
       let text = "";
       for await (const event of events) {
@@ -75,7 +94,10 @@ const teams = createTeamsChannelAdapter({
         }
       }
 
-      await ctx.sendInvoke(createTeamsDialogMessage(text));
+      return {
+        status: 200,
+        body: createTeamsDialogMessage(text),
+      };
     },
   },
 });
@@ -103,11 +125,200 @@ Read Teams metadata from tools or middleware during a turn.
 Send a Teams invoke response body without manually constructing an
 `invokeResponse` activity.
 
+Invoke handlers can also return a `TeamsInvokeResult` directly. If a handled
+invoke returns nothing, the adapter sends an empty `200` acknowledgement. If no
+Teams handler handles the invoke, the adapter returns an explicit `501`.
+
 ### `createTeamsDialog(...)` and `createTeamsSearchResult(...)`
 
 Build common Teams dialog/search invoke bodies without making callers hand-roll
 raw payload objects.
 
+## TeamsInfo and Typed Channel Data
+
+The curated Teams helper surface is available directly from the main barrel. If
+you prefer a grouped import path, the same exports are also available from the
+`./extensions` subpath.
+
+These helpers do not require `AgentApplication`; they work with the same
+`TurnContext` already used by the cuylabs adapter layer.
+
+```ts
+import {
+  TeamsInfo,
+  TeamsAttachmentDownloader,
+  parseTeamsChannelData,
+} from "@cuylabs/agent-channel-teams";
+
+const teams = createTeamsChannelAdapter({
+  agent,
+  handlers: {
+    async dialogSubmit(ctx) {
+      const members = await TeamsInfo.getPagedMembers(ctx.turnContext);
+      const names = members.members.map((m) => m.name).join(", ");
+      await ctx.sendInvoke(createTeamsDialogMessage(`Team members: ${names}`));
+    },
+  },
+});
+
+// Zod-validated typed channel data
+const channelData = parseTeamsChannelData(ctx.turnContext.activity.channelData);
+console.log(channelData.team?.id, channelData.tenant?.id);
+```
+
+`parseTeamsChannelData()` is intentionally strict. If the incoming Teams payload
+does not match the expected SDK shape, parsing fails fast instead of silently
+dropping typed data.
+
+The same helpers are also grouped under:
+
+```ts
+import {
+  TeamsInfo,
+  parseTeamsChannelData,
+} from "@cuylabs/agent-channel-teams/extensions";
+```
+
+Type-only imports are available from the main barrel:
+
+```ts
+import type {
+  TeamDetails,
+  TeamsChannelData,
+  TeamsMeetingInfo,
+} from "@cuylabs/agent-channel-teams";
+```
+
+Handler and `prepareTurn()` contexts also expose parsed channel data directly:
+
+```ts
+const teams = createTeamsChannelAdapter({
+  agent,
+  prepareTurn: ({ teams, channelData }) => ({
+    system: `Tenant: ${channelData?.tenant?.id ?? teams.tenantId ?? "unknown"}`,
+  }),
+  handlers: {
+    meetingStart(ctx) {
+      console.log(ctx.channelData?.meeting?.id ?? ctx.teams.meetingId);
+    },
+  },
+});
+```
+
+## Meeting Handlers
+
+Meeting events are dispatched through the same `handlers` object as other Teams activities. Meeting events are `Event`-type activities (except `meetingStageView` and `meetingSmartReply` which are `Invoke`-type).
+
+```ts
+const teams = createTeamsChannelAdapter({
+  agent,
+  handlers: {
+    meetingStart(ctx) {
+      console.log("Meeting started:", ctx.teams.meetingId);
+    },
+    meetingEnd(ctx) {
+      console.log("Meeting ended:", ctx.teams.meetingId);
+    },
+    participantsJoin(ctx) {
+      console.log("Participants joined");
+    },
+    participantsLeave(ctx) {
+      console.log("Participants left");
+    },
+  },
+});
+```
+
+All 17 meeting event kinds from Microsoft's SDK are supported:
+
+| Handler                   | Activity type | Teams event name          |
+| ------------------------- | ------------- | ------------------------- |
+| `meetingStart`            | Event         | `meetingStart`            |
+| `meetingEnd`              | Event         | `meetingEnd`              |
+| `participantsJoin`        | Event         | `meetingParticipantJoin`  |
+| `participantsLeave`       | Event         | `meetingParticipantLeave` |
+| `meetingRoomJoin`         | Event         | `meetingRoomJoin`         |
+| `meetingRoomLeave`        | Event         | `meetingRoomLeave`        |
+| `meetingReaction`         | Event         | `meetingReaction`         |
+| `meetingPollResponse`     | Event         | `meetingPollResponse`     |
+| `meetingAppsInstalled`    | Event         | `meetingAppsInstalled`    |
+| `meetingAppsUninstalled`  | Event         | `meetingAppsUninstalled`  |
+| `meetingRecordingStarted` | Event         | `meetingRecordingStarted` |
+| `meetingRecordingStopped` | Event         | `meetingRecordingStopped` |
+| `meetingFocusChange`      | Event         | `meetingFocusChange`      |
+| `meetingScreenShareStart` | Event         | `meetingScreenShareStart` |
+| `meetingScreenShareStop`  | Event         | `meetingScreenShareStop`  |
+| `meetingStageView`        | Invoke        | `meetingStageView`        |
+| `meetingSmartReply`       | Invoke        | `meetingSmartReply`       |
+
+The event-name mappings are exported for hosts that need explicit routing or
+observability constants:
+
+```ts
+import {
+  TEAMS_MEETING_EVENT_NAMES,
+  TEAMS_MEETING_INVOKE_NAMES,
+} from "@cuylabs/agent-channel-teams";
+```
+
+## Handler Capability Groups
+
+For larger apps, the handler interfaces are also grouped by capability:
+
+- `TeamsMessageActivityHandlers`
+- `TeamsConversationUpdateHandlers`
+- `TeamsCardActionHandlers`
+- `TeamsConfigHandlers`
+- `TeamsTaskModuleHandlers`
+- `TeamsMessageExtensionHandlers`
+- `TeamsTabHandlers`
+- `TeamsMeetingHandlers`
+
+`TeamsActivityHandlers` composes these groups into the full Teams surface.
+
+## `onTurn` Middleware Hook
+
+For advanced use cases where you need raw `TurnContext` access before cuylabs processing — for example, to use Microsoft SDK helpers directly or to short-circuit certain activity types — use the `onTurn` hook:
+
+```ts
+const teams = createTeamsChannelAdapter({
+  agent,
+  onTurn: async (context, next) => {
+    console.log(
+      `Activity: ${context.activity.type} / ${context.activity.name}`,
+    );
+
+    // Call next() to continue into the normal handler pipeline
+    await next();
+  },
+  handlers: {
+    // ...
+  },
+});
+```
+
+You can short-circuit by not calling `next()`:
+
+```ts
+onTurn: async (context, next) => {
+  if (shouldSkip(context)) {
+    // Don't call next() — cuylabs processing is skipped entirely
+    return;
+  }
+  await next();
+},
+```
+
+## Docs
+
+The package README is the quick-start view. For the focused concept guides, use
+the docs set:
+
+- [docs/README.md](docs/README.md) for the documentation index
+- [docs/architecture.md](docs/architecture.md) for the bridge boundary and layering
+- [docs/handler-model.md](docs/handler-model.md) for handler groups, meeting routing, and `onTurn`
+- [docs/teams-helpers.md](docs/teams-helpers.md) for `TeamsInfo`, typed channel data, and the curated helper surface
+
 ## Why This Package Exists
 
 This package is the bridge between:
@@ -119,3 +330,9 @@ This package is the bridge between:
 That means you can start with ordinary Teams bot chat now, and then add
 dialogs, message actions, or search-oriented Teams invokes without changing
 your core agent architecture.
+
+The important boundary is:
+
+- Microsoft SDK helpers and DTOs are available where they fit naturally
+- `agent-core` remains the only execution engine
+- `AgentApplication`, `Meeting`, `TaskModule`, and similar Microsoft router classes are intentionally not part of the public cuylabs model

package/dist/chunk-B5KRH22J.js

@@ -0,0 +1,12 @@
+// src/extensions.ts
+import {
+  TeamsAttachmentDownloader,
+  TeamsInfo
+} from "@microsoft/agents-hosting-extensions-teams";
+import { parseTeamsChannelData } from "@microsoft/agents-hosting-extensions-teams";
+
+export {
+  TeamsAttachmentDownloader,
+  TeamsInfo,
+  parseTeamsChannelData
+};

package/dist/extensions.d.ts

@@ -0,0 +1 @@
+export { BatchFailedEntriesResponse, BatchOperationResponse, BatchOperationStateResponse, CancelOperationResponse, ChannelInfo, FeedbackLoopData, MeetingNotification, NotificationInfo, OnBehalfOf, TeamDetails, TeamInfo, TeamsAttachmentDownloader, TeamsChannelAccount, TeamsChannelData, TeamsChannelDataSettings, TeamsInfo, TeamsMeetingInfo, TeamsMember, TeamsPagedMembersResult, TenantInfo, parseTeamsChannelData } from '@microsoft/agents-hosting-extensions-teams';

package/dist/extensions.js

@@ -0,0 +1,10 @@
+import {
+  TeamsAttachmentDownloader,
+  TeamsInfo,
+  parseTeamsChannelData
+} from "./chunk-B5KRH22J.js";
+export {
+  TeamsAttachmentDownloader,
+  TeamsInfo,
+  parseTeamsChannelData
+};

package/dist/index.d.ts

@@ -1,12 +1,21 @@
 import { AgentEvent } from '@cuylabs/agent-core';
 import { M365ChannelOptions, M365TurnRequestContext, M365TurnPreparation, M365UserIdentity, M365TurnSource, M365ChannelAdapter, M365AmbientTurnContext } from '@cuylabs/agent-channel-m365';
 import { TurnContext, AuthConfiguration, CloudAdapter } from '@microsoft/agents-hosting';
+import { TeamsChannelData } from '@microsoft/agents-hosting-extensions-teams';
+export { BatchFailedEntriesResponse, BatchOperationResponse, BatchOperationStateResponse, CancelOperationResponse, ChannelInfo, FeedbackLoopData, MeetingNotification, NotificationInfo, OnBehalfOf, TeamDetails, TeamInfo, TeamsAttachmentDownloader, TeamsChannelAccount, TeamsChannelData, TeamsChannelDataSettings, TeamsInfo, TeamsMeetingInfo, TeamsMember, TeamsPagedMembersResult, TenantInfo, parseTeamsChannelData } from '@microsoft/agents-hosting-extensions-teams';
+import { Activity, Attachment } from '@microsoft/agents-activity';
 import { Server } from 'node:http';
 import { Application } from 'express';
-import { Activity, Attachment } from '@microsoft/agents-activity';
+
+interface TeamsInvokeResult<T = unknown> {
+    status: number;
+    body?: T;
+}
+declare function createTeamsInvokeActivity<T = unknown>(result: TeamsInvokeResult<T>): Activity;
+declare function sendTeamsInvoke<T = unknown>(context: TurnContext, body?: T, status?: number): Promise<void>;
 
 type TeamsSurface = "personal" | "channel" | "group" | "meeting" | "unknown";
-type TeamsActivityKind = "message" | "message-edit" | "message-delete" | "message-restore" | "reaction" | "card-submit" | "feedback" | "dialog-open" | "dialog-submit" | "search-command" | "select-result" | "invoke" | "conversation-update" | "other";
+type TeamsActivityKind = "message" | "conversation-update" | "members-added" | "members-removed" | "channel-created" | "channel-deleted" | "channel-renamed" | "channel-restored" | "channel-shared" | "channel-unshared" | "team-renamed" | "team-archived" | "team-unarchived" | "team-deleted" | "team-hard-deleted" | "team-restored" | "message-edit" | "message-delete" | "message-restore" | "reaction" | "read-receipt" | "config-fetch" | "config-submit" | "file-consent" | "actionable-message-execute-action" | "card-submit" | "feedback" | "dialog-open" | "dialog-submit" | "task-fetch" | "task-submit" | "search-command" | "message-extension-query" | "message-extension-query-link" | "message-extension-anonymous-query-link" | "select-result" | "message-extension-select-item" | "message-extension-submit-action" | "message-extension-fetch-task" | "message-extension-query-setting-url" | "message-extension-setting" | "message-extension-card-button-clicked" | "tab-fetch" | "tab-submit" | "invoke" | "meeting-start" | "meeting-end" | "participants-join" | "participants-leave" | "meeting-room-join" | "meeting-room-leave" | "meeting-stage-view" | "meeting-smart-reply" | "meeting-reaction" | "meeting-poll-response" | "meeting-apps-installed" | "meeting-apps-uninstalled" | "meeting-recording-started" | "meeting-recording-stopped" | "meeting-focus-change" | "meeting-screen-share-start" | "meeting-screen-share-stop" | "other";
 interface TeamsActorReference {
     id?: string;
     displayName?: string;
@@ -25,19 +34,21 @@ interface TeamsActivityInfo {
     teamId?: string;
     channelThreadId?: string;
     meetingId?: string;
+    channelData?: TeamsChannelData;
     surface: TeamsSurface;
     kind: TeamsActivityKind;
     actors: TeamsActorReference[];
 }
 interface TeamsTurnRequestContext extends M365TurnRequestContext {
     teams: TeamsActivityInfo;
+    channelData?: TeamsChannelData;
 }
 type TeamsTurnPreparation = M365TurnPreparation;
-type TeamsHandlerDecision = void | "continue";
 interface TeamsHandlerContext {
     turnContext: TurnContext;
     user: M365UserIdentity;
     teams: TeamsActivityInfo;
+    channelData?: TeamsChannelData;
     sessionId: string;
     source: M365TurnSource;
     /**
@@ -55,18 +66,109 @@ interface TeamsHandlerContext {
      */
     sendInvoke(body?: unknown, status?: number): Promise<void>;
 }
-interface TeamsActivityHandlers {
-    messageEdited?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    messageDeleted?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    messageRestored?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    reaction?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    cardSubmit?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    feedbackSubmit?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    dialogOpen?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    dialogSubmit?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    searchCommand?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    selectResult?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
-    invoke?: (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
+type TeamsHandlerDecision = void | "continue" | TeamsInvokeResult;
+type TeamsActivityHandler = (context: TeamsHandlerContext) => TeamsHandlerDecision | Promise<TeamsHandlerDecision>;
+interface TeamsConversationUpdateHandlers {
+    conversationUpdate?: TeamsActivityHandler;
+    membersAdded?: TeamsActivityHandler;
+    membersRemoved?: TeamsActivityHandler;
+    channelCreated?: TeamsActivityHandler;
+    channelDeleted?: TeamsActivityHandler;
+    channelRenamed?: TeamsActivityHandler;
+    channelRestored?: TeamsActivityHandler;
+    channelShared?: TeamsActivityHandler;
+    channelUnshared?: TeamsActivityHandler;
+    teamRenamed?: TeamsActivityHandler;
+    teamArchived?: TeamsActivityHandler;
+    teamUnarchived?: TeamsActivityHandler;
+    teamDeleted?: TeamsActivityHandler;
+    teamHardDeleted?: TeamsActivityHandler;
+    teamRestored?: TeamsActivityHandler;
+}
+interface TeamsMessageActivityHandlers {
+    messageEdited?: TeamsActivityHandler;
+    messageDeleted?: TeamsActivityHandler;
+    messageRestored?: TeamsActivityHandler;
+    reaction?: TeamsActivityHandler;
+    readReceipt?: TeamsActivityHandler;
+}
+interface TeamsCardActionHandlers {
+    cardSubmit?: TeamsActivityHandler;
+    feedbackSubmit?: TeamsActivityHandler;
+    fileConsent?: TeamsActivityHandler;
+    actionableMessageExecuteAction?: TeamsActivityHandler;
+}
+interface TeamsConfigHandlers {
+    configFetch?: TeamsActivityHandler;
+    configSubmit?: TeamsActivityHandler;
+}
+interface TeamsTaskModuleHandlers {
+    dialogOpen?: TeamsActivityHandler;
+    dialogSubmit?: TeamsActivityHandler;
+    taskFetch?: TeamsActivityHandler;
+    taskSubmit?: TeamsActivityHandler;
+}
+interface TeamsMessageExtensionHandlers {
+    searchCommand?: TeamsActivityHandler;
+    selectResult?: TeamsActivityHandler;
+    messageExtensionQuery?: TeamsActivityHandler;
+    messageExtensionQueryLink?: TeamsActivityHandler;
+    messageExtensionAnonymousQueryLink?: TeamsActivityHandler;
+    messageExtensionSelectItem?: TeamsActivityHandler;
+    messageExtensionSubmitAction?: TeamsActivityHandler;
+    messageExtensionFetchTask?: TeamsActivityHandler;
+    messageExtensionQuerySettingUrl?: TeamsActivityHandler;
+    messageExtensionSetting?: TeamsActivityHandler;
+    messageExtensionCardButtonClicked?: TeamsActivityHandler;
+}
+interface TeamsTabHandlers {
+    tabFetch?: TeamsActivityHandler;
+    tabSubmit?: TeamsActivityHandler;
+}
+interface TeamsMeetingHandlers {
+    /** Fired when a Teams meeting starts. */
+    meetingStart?: TeamsActivityHandler;
+    /** Fired when a Teams meeting ends. */
+    meetingEnd?: TeamsActivityHandler;
+    /** Fired when participants join a Teams meeting. */
+    participantsJoin?: TeamsActivityHandler;
+    /** Fired when participants leave a Teams meeting. */
+    participantsLeave?: TeamsActivityHandler;
+    /** Fired when a physical meeting room joins a Teams meeting. */
+    meetingRoomJoin?: TeamsActivityHandler;
+    /** Fired when a physical meeting room leaves a Teams meeting. */
+    meetingRoomLeave?: TeamsActivityHandler;
+    /** Fired when the app is viewed in the meeting stage (invoke). */
+    meetingStageView?: TeamsActivityHandler;
+    /** Fired for smart reply recommendations during a meeting (invoke). */
+    meetingSmartReply?: TeamsActivityHandler;
+    /** Fired for emoji reactions during a meeting. */
+    meetingReaction?: TeamsActivityHandler;
+    /** Fired when a poll response is submitted during a meeting. */
+    meetingPollResponse?: TeamsActivityHandler;
+    /** Fired when apps are installed during a meeting. */
+    meetingAppsInstalled?: TeamsActivityHandler;
+    /** Fired when apps are uninstalled during a meeting. */
+    meetingAppsUninstalled?: TeamsActivityHandler;
+    /** Fired when meeting recording starts. */
+    meetingRecordingStarted?: TeamsActivityHandler;
+    /** Fired when meeting recording stops. */
+    meetingRecordingStopped?: TeamsActivityHandler;
+    /** Fired when the meeting focus changes. */
+    meetingFocusChange?: TeamsActivityHandler;
+    /** Fired when screen sharing starts in a meeting. */
+    meetingScreenShareStart?: TeamsActivityHandler;
+    /** Fired when screen sharing stops in a meeting. */
+    meetingScreenShareStop?: TeamsActivityHandler;
+}
+/**
+ * Aggregate Teams handler surface grouped by capability.
+ *
+ * This keeps the public API centered on Teams concepts without exposing
+ * Microsoft's `AgentApplication` routing types.
+ */
+interface TeamsActivityHandlers extends TeamsConversationUpdateHandlers, TeamsMessageActivityHandlers, TeamsCardActionHandlers, TeamsConfigHandlers, TeamsTaskModuleHandlers, TeamsMessageExtensionHandlers, TeamsTabHandlers, TeamsMeetingHandlers {
+    invoke?: TeamsActivityHandler;
 }
 interface TeamsChannelOptions extends Omit<M365ChannelOptions, "prepareTurn"> {
     /**
@@ -77,11 +179,21 @@ interface TeamsChannelOptions extends Omit<M365ChannelOptions, "prepareTurn"> {
     /**
      * Teams-specific activity hooks that run before generic M365 handling.
      *
-     * Note: the `"feedback"` kind falls through to `cardSubmit` when
-     * `feedbackSubmit` is not defined. Define `feedbackSubmit` explicitly
-     * if you need to distinguish feedback actions from card submits.
+     * Notes:
+     * - the `"feedback"` kind falls through to `cardSubmit` when
+     *   `feedbackSubmit` is not defined
+     * - specialized Teams invoke kinds fall back to grouped handlers such as
+     *   `dialogOpen`, `searchCommand`, or `selectResult` when the narrow handler
+     *   is not provided
      */
     handlers?: TeamsActivityHandlers;
+    /**
+     * General-purpose middleware that runs on every turn before cuylabs
+     * processing. Gives raw `TurnContext` access for Microsoft SDK helpers
+     * or custom logic. Call `next()` to continue into the normal handler
+     * pipeline, or return without calling it to short-circuit.
+     */
+    onTurn?: (context: TurnContext, next: () => Promise<void>) => Promise<void>;
 }
 interface TeamsChannelAdapter extends M365ChannelAdapter {
     /**
@@ -114,13 +226,6 @@ interface TeamsAmbientTurnContext extends M365AmbientTurnContext {
 declare function currentTeamsTurnContext(): Readonly<TeamsAmbientTurnContext> | undefined;
 declare function runWithTeamsTurnContext<T>(value: TeamsAmbientTurnContext, fn: () => T | Promise<T>): Promise<T>;
 
-interface TeamsInvokeResult<T = unknown> {
-    status: number;
-    body?: T;
-}
-declare function createTeamsInvokeActivity<T = unknown>(result: TeamsInvokeResult<T>): Activity;
-declare function sendTeamsInvoke<T = unknown>(context: TurnContext, body?: T, status?: number): Promise<void>;
-
 type TeamsSearchLayout = "list" | "grid";
 type TeamsSearchResultType = "result" | "auth" | "config" | "message" | "botMessagePreview" | "silentAuth";
 interface TeamsSearchAttachment extends Attachment {
@@ -177,6 +282,25 @@ interface TeamsDialogMessageBody {
 declare function createTeamsDialog(dialog: TeamsDialogDefinition): TeamsDialogResponse;
 declare function createTeamsDialogMessage(message: string): TeamsDialogMessageBody;
 
+declare const TEAMS_CONFIG_FETCH_NAMES: readonly ["config/fetch"];
+declare const TEAMS_CONFIG_SUBMIT_NAMES: readonly ["config/submit"];
+declare const TEAMS_FILE_CONSENT_NAMES: readonly ["fileConsent/invoke"];
+declare const TEAMS_ACTIONABLE_MESSAGE_NAMES: readonly ["actionableMessage/executeAction"];
+declare const TEAMS_TASK_MODULE_FETCH_NAMES: readonly ["task/fetch", "composeExtension/fetchTask"];
+declare const TEAMS_TASK_MODULE_SUBMIT_NAMES: readonly ["task/submit"];
+declare const TEAMS_TAB_FETCH_NAMES: readonly ["tab/fetch"];
+declare const TEAMS_TAB_SUBMIT_NAMES: readonly ["tab/submit"];
+declare const TEAMS_MESSAGE_EXTENSION_QUERY_NAMES: readonly ["composeExtension/query", "composeExtension/queryLink", "composeExtension/anonymousQueryLink"];
+declare const TEAMS_MESSAGE_EXTENSION_SUBMIT_ACTION_NAMES: readonly ["composeExtension/submitAction"];
+declare const TEAMS_MESSAGE_EXTENSION_FETCH_TASK_NAMES: readonly ["composeExtension/fetchTask"];
+declare const TEAMS_MESSAGE_EXTENSION_QUERY_SETTING_URL_NAMES: readonly ["composeExtension/querySettingUrl"];
+declare const TEAMS_MESSAGE_EXTENSION_SETTING_NAMES: readonly ["composeExtension/setting"];
+declare const TEAMS_MESSAGE_EXTENSION_CARD_BUTTON_CLICKED_NAMES: readonly ["composeExtension/onCardButtonClicked"];
+declare const TEAMS_MESSAGE_EXTENSION_SELECT_NAMES: readonly ["composeExtension/selectItem"];
+declare const TEAMS_CARD_ACTION_SUBMIT_NAMES: readonly ["message/submitAction"];
+declare const TEAMS_CONVERSATION_UPDATE_EVENT_NAMES: Readonly<Record<string, TeamsActivityKind>>;
+declare const TEAMS_MEETING_EVENT_NAMES: Readonly<Record<string, TeamsActivityKind>>;
+declare const TEAMS_MEETING_INVOKE_NAMES: Readonly<Record<string, TeamsActivityKind>>;
 declare function parseTeamsActivity(context: TurnContext): TeamsActivityInfo;
 
-export { type MountTeamsAgentOptions, type MountTeamsAgentResult, type TeamsActivityHandlers, type TeamsActivityInfo, type TeamsActivityKind, type TeamsActorReference, type TeamsAmbientTurnContext, type TeamsChannelAdapter, type TeamsChannelOptions, type TeamsDialogDefinition, type TeamsDialogMessageBody, type TeamsDialogResponse, type TeamsDialogSize, type TeamsHandlerContext, type TeamsHandlerDecision, type TeamsInvokeResult, type TeamsSearchAttachment, type TeamsSearchLayout, type TeamsSearchMessageBody, type TeamsSearchResponse, type TeamsSearchResult, type TeamsSearchResultBody, type TeamsSearchResultType, type TeamsSurface, type TeamsTurnPreparation, type TeamsTurnRequestContext, createTeamsChannelAdapter, createTeamsDialog, createTeamsDialogMessage, createTeamsInvokeActivity, createTeamsSearchMessage, createTeamsSearchResult, currentTeamsTurnContext, mountTeamsAgent, parseTeamsActivity, runWithTeamsTurnContext, sendTeamsInvoke };
+export { type MountTeamsAgentOptions, type MountTeamsAgentResult, TEAMS_ACTIONABLE_MESSAGE_NAMES, TEAMS_CARD_ACTION_SUBMIT_NAMES, TEAMS_CONFIG_FETCH_NAMES, TEAMS_CONFIG_SUBMIT_NAMES, TEAMS_CONVERSATION_UPDATE_EVENT_NAMES, TEAMS_FILE_CONSENT_NAMES, TEAMS_MEETING_EVENT_NAMES, TEAMS_MEETING_INVOKE_NAMES, TEAMS_MESSAGE_EXTENSION_CARD_BUTTON_CLICKED_NAMES, TEAMS_MESSAGE_EXTENSION_FETCH_TASK_NAMES, TEAMS_MESSAGE_EXTENSION_QUERY_NAMES, TEAMS_MESSAGE_EXTENSION_QUERY_SETTING_URL_NAMES, TEAMS_MESSAGE_EXTENSION_SELECT_NAMES, TEAMS_MESSAGE_EXTENSION_SETTING_NAMES, TEAMS_MESSAGE_EXTENSION_SUBMIT_ACTION_NAMES, TEAMS_TAB_FETCH_NAMES, TEAMS_TAB_SUBMIT_NAMES, TEAMS_TASK_MODULE_FETCH_NAMES, TEAMS_TASK_MODULE_SUBMIT_NAMES, type TeamsActivityHandler, type TeamsActivityHandlers, type TeamsActivityInfo, type TeamsActivityKind, type TeamsActorReference, type TeamsAmbientTurnContext, type TeamsCardActionHandlers, type TeamsChannelAdapter, type TeamsChannelOptions, type TeamsConfigHandlers, type TeamsConversationUpdateHandlers, type TeamsDialogDefinition, type TeamsDialogMessageBody, type TeamsDialogResponse, type TeamsDialogSize, type TeamsHandlerContext, type TeamsHandlerDecision, type TeamsInvokeResult, type TeamsMeetingHandlers, type TeamsMessageActivityHandlers, type TeamsMessageExtensionHandlers, type TeamsSearchAttachment, type TeamsSearchLayout, type TeamsSearchMessageBody, type TeamsSearchResponse, type TeamsSearchResult, type TeamsSearchResultBody, type TeamsSearchResultType, type TeamsSurface, type TeamsTabHandlers, type TeamsTaskModuleHandlers, type TeamsTurnPreparation, type TeamsTurnRequestContext, createTeamsChannelAdapter, createTeamsDialog, createTeamsDialogMessage, createTeamsInvokeActivity, createTeamsSearchMessage, createTeamsSearchResult, currentTeamsTurnContext, mountTeamsAgent, parseTeamsActivity, runWithTeamsTurnContext, sendTeamsInvoke };