@open-everywhere/provider-teams 0.0.0-stage → 0.1.1

package/dist/agent/channels/teams-input-response.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-input-response.js","sourceRoot":"","sources":["../../../agent/channels/teams-input-response.ts"],"names":[],"mappings":"AAAA,wDAAwD;AACxD,EAAE;AACF,8FAA8F;AAC9F,qGAAqG;AACrG,gGAAgG;AAChG,oGAAoG;AACpG,8FAA8F;AAC9F,kGAAkG;AAClG,2FAA2F;AAC3F,2EAA2E;AAC3E,EAAE;AACF,6FAA6F;AAC7F,iGAAiG;AACjG,+FAA+F;AAC/F,mGAAmG;AACnG,yFAAyF;AACzF,mGAAmG;AACnG,oCAAoC;AACpC,EAAE;AACF,mGAAmG;AACnG,mGAAmG;AACnG,EAAE;AACF,+FAA+F;AAC/F,oGAAoG;AACpG,oGAAoG;AACpG,gGAAgG;AAChG,oGAAoG;AACpG,gGAAgG;AAChG,sDAAsD;AAGtD,OAAO,EACL,kBAAkB,EAClB,gBAAgB,EAChB,gBAAgB,GAMjB,MAAM,4CAA4C,CAAC;AACpD,OAAO,EAAE,cAAc,EAAE,mBAAmB,EAAE,MAAM,qBAAqB,CAAC;AAC1E,OAAO,EAAE,oBAAoB,EAAE,sBAAsB,EAAE,MAAM,mBAAmB,CAAC;AAejF;;;;;;GAMG;AACH,MAAM,CAAC,KAAK,UAAU,uBAAuB,CAC3C,GAAiB,EACjB,QAAoD,EACpD,IAAI,GAA2B,EAAE;IAEjC,MAAM,KAAK,GAAG,IAAI,CAAC,QAAQ,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,oBAAoB,CAAC,sBAAsB,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,YAAY,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC;IAC9H,IAAI,IAAmD,CAAC;IACxD,IAAI,CAAC;QACH,MAAM,QAAQ,GAAG,MAAM,KAAK,CAAC,QAAQ,CAAC,CAAC;QACvC,IAAI,GAAG,cAAc,CAAC;YACpB,MAAM,EAAE,QAAQ,CAAC,IAAI,CAAC,EAAE;YACxB,WAAW,EAAE,QAAQ,CAAC,IAAI,CAAC,WAAW;YACtC,QAAQ,EAAE,QAAQ,CAAC,IAAI,CAAC,IAAI;YAC5B,QAAQ,EAAE,QAAQ,CAAC,QAAQ,IAAI,QAAQ,CAAC,YAAY,CAAC,QAAQ;YAC7D,cAAc,EAAE,QAAQ,CAAC,YAAY,CAAC,EAAE;YACxC,SAAS,EAAE,QAAQ,CAAC,cAAc;YAClC,MAAM,EAAE,QAAQ,CAAC,MAAM;YACvB,UAAU,EAAE,QAAQ,CAAC,UAAU;YAC/B,KAAK,EAAE,QAAQ,CAAC,KAAK;YACrB,cAAc,EAAE,mBAAmB,CAAC,QAAQ,CAAC,WAAW,CAAC;YACzD,QAAQ;SACT,CAAC,CAAC;QACH,MAAM,QAAQ,GAAG;YACf,OAAO,EAAE,EAAE,IAAI,EAAE,OAAO,EAAE;YAC1B,OAAO,EAAE,EAAE,IAAI,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE,EAAE;SAClB,CAAC;QACrB,MAAM,CAAC,GAAG,gBAAgB,CAAC,QAAQ,CAAC,CAAC;QAErC,0FAA0F;QAC1F,6FAA6F;QAC7F,+FAA+F;QAC/F,0BAA0B;QAC1B,MAAM,SAAS,GAAG,IAAI,CAAC,SAAS,IAAI,gBAAgB,CAAC;QACrD,MAAM,YAAY,GAAG,MAAM,SAAS,CAAC;YACnC,QAAQ;YACR,IAAI,EAAE,QAAQ;YACd,WAAW,EAAE,QAAQ,CAAC,IAAI,CAAC,EAAE;YAC7B,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,EAAE,GAAG,MAAM,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;SACvD,CAAC,CAAC;QACH,IAAI,YAAY,KAAK,UAAU;YAAE,OAAO,IAAI,CAAC;QAE7C,MAAM,OAAO,GAAG,MAAM,CAAC,IAAI,CAAC,KAAK,IAAI,kBAAkB,CAAC,CAAC;YACvD,GAAG,EAAE,CAAC,CAAC,GAAG;YACV,QAAQ,EAAE,CAAC,CAAC,QAAQ;YACpB,SAAS,EAAE,CAAC,CAAC,SAAS;YACtB,OAAO,EAAE,CAAC,CAAC,OAAO;YAClB,UAAU,EAAE,CAAC,CAAC,UAAU;YACxB,WAAW,EAAE,QAAQ,CAAC,IAAI,CAAC,EAAE;YAC7B,6FAA6F;YAC7F,4FAA4F;YAC5F,GAAG,CAAC,QAAQ,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,EAAE,eAAe,EAAE,QAAQ,KAAK,OAAO,EAAE,CAAC;SAC7E,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,EAAE;YAAE,OAAO,EAAE,IAAI,EAAE,CAAC;QAChC,MAAM,MAAM,GAAG,IAAI,CAAC,MAAM,IAAI,CAAC,KAAK,EAAE,IAAY,EAAiB,EAAE,GAAG,MAAM,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC;QACxG,MAAM,MAAM,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,CAAC,CAAC,GAAY,EAAE,EAAE;YAClD,OAAO,CAAC,KAAK,CAAC,+DAA+D,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QAC9F,CAAC,CAAC,CAAC;QACH,OAAO,IAAI,CAAC;IACd,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,OAAO,CAAC,KAAK,CAAC,uFAAuF,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;QACpH,2FAA2F;QAC3F,+DAA+D;QAC/D,OAAO,EAAE,IAAI,EAAE,IAAI,IAAI,IAAI,EAAE,CAAC;IAChC,CAAC;AACH,CAAC"}

package/dist/agent/channels/teams-message-ops.d.ts

@@ -0,0 +1,3 @@
+import type { SurfaceMessageOps } from "@open-everywhere/core/agent/adapter-api.js";
+export declare const teamsMessageOps: SurfaceMessageOps;
+//# sourceMappingURL=teams-message-ops.d.ts.map

package/dist/agent/channels/teams-message-ops.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-message-ops.d.ts","sourceRoot":"","sources":["../../../agent/channels/teams-message-ops.ts"],"names":[],"mappings":"AA6BA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,4CAA4C,CAAC;AAyBpF,eAAO,MAAM,eAAe,EAAE,iBAwB7B,CAAC"}

package/dist/agent/channels/teams-message-ops.js

@@ -0,0 +1,72 @@
+// teams-message-ops — Teams's SurfaceMessageOps (OPE-899): the ancillary message ops core features
+// dispatch through channels/surface-message-ops.ts. Before this file, Teams registered none, so the
+// stop acknowledgement (turn-anchor.ts's `postSurfaceText`) resolved nothing on a Teams turn — the
+// stop control worked (teams-stop.ts, the `angry` reaction), it was just invisible: a person who
+// reacted saw the agent go quiet and read nothing.
+//
+//   - postText    → the SAME Bot-Framework send/reply the mid-turn post arm uses
+//                   (teams-post-arm.ts's `dispatchTeamsReply`, exported for this file — one
+//                   mint/send implementation, never a second copy).
+//   - editMessage → the SAME update-activity call `edit_reply` performs (`editTeamsMessage`).
+//   - NO `postFiles` (register.ts already records: "NO attachment resolver — the Teams surface
+//     carries no attachment plane today"). The optional tier exists exactly for this shape.
+//   - NO `setReaction` (register.ts: "NO reaction surface — Teams has no integration reaction
+//     primitive"). The `angry` reaction (teams-stop.ts) IS Teams's stop affordance; there is no
+//     second glyph to place beside it.
+//
+// THE PROBLEM THIS FILE SOLVES, IN ONE SENTENCE: `SurfaceMessageOps.postText`/`editMessage` are
+// handed only a bare `channelId` (core's `channelId` is Teams's conversation id — see
+// `turn-anchor.ts`'s `turnAnchorAddress`), never a `serviceUrl`, and a Bot-Framework write needs
+// BOTH. `teams-conversation-ref.ts`'s `conversation`-grain address (OPE-899's addition to that
+// module) is the lookup that answers it: every inbound activity, on every scope, stamps a row keyed
+// on its EXACT conversation id, so the reply chain a channel turn anchored on is resolvable here by
+// that same id.
+//
+// `opts.replyToMessageId` on `postText` threads the post via `replyToActivityId` — the SAME field
+// the mid-turn reply arm anchors on. `turn-anchor.ts`'s own cancel-note call passes no such option
+// (a top-level post, like every other surface's cancel note today), so this is exercised by other
+// SurfaceMessageOps consumers (the approval decision notice), not by the stop path itself.
+import { dispatchTeamsReply, editTeamsMessage } from "./teams-post-arm.js";
+import { teamsConversationRef } from "./teams-conversation-ref.js";
+import { restoreTeamsConversationId } from "./teams-id-restore.js";
+/**
+ * The stored `conversation`-grain reference for `channelId`, or a loud, honest refusal — never a
+ * guessed target. Mirrors `github-message-ops.ts`'s `requireContainer`.
+ *
+ * 🔴 IT RESTORES THE RAW ID FIRST (OPE-1078). `channelId` reaches here in one of two spellings: raw,
+ * from a live turn's own anchor, or the SURFACE-KEY spelling, from a granted `teams:channel/<id>`
+ * address — the only spelling the resource-grant grammar admits. `restoreTeamsConversationId` is the
+ * identity on the first and the index lookup on the second, so both land on the same reference. The
+ * refusal below still names the id the CALLER gave, which is the one an operator can act on.
+ */
+async function requireConversationRef(channelId) {
+    const ref = await teamsConversationRef(await restoreTeamsConversationId(channelId));
+    if (!ref) {
+        throw new Error(`Teams surface message ops: no conversation reference for "${channelId}" — this deployment has never seen an inbound activity on that id.`);
+    }
+    return ref;
+}
+export const teamsMessageOps = {
+    platform: "teams",
+    /** Post through the mid-turn reply transport, resolving `serviceUrl` from the stored conversation
+     *  reference. `opts?.replyToMessageId` threads the post — see the header. */
+    async postText(channelId, text, opts) {
+        const { serviceUrl, conversationId } = await requireConversationRef(channelId);
+        const target = {
+            platform: "teams",
+            serviceUrl,
+            conversationId,
+            ...(opts?.replyToMessageId ? { replyToActivityId: opts.replyToMessageId } : {}),
+        };
+        return dispatchTeamsReply(target, text);
+    },
+    /** Update the given activity in place — the same transport `edit_reply` performs on the reply
+     *  spine, resolving `serviceUrl` the same way `postText` does. It sends the RESOLVED conversation
+     *  id, never the caller's, for the reason `requireConversationRef` states: the caller's may be the
+     *  surface-key spelling, and the Connector accepts only the raw id. */
+    async editMessage(channelId, messageId, text) {
+        const { serviceUrl, conversationId } = await requireConversationRef(channelId);
+        await editTeamsMessage({ platform: "teams", channelId: conversationId, serviceUrl }, messageId, text);
+    },
+};
+//# sourceMappingURL=teams-message-ops.js.map

package/dist/agent/channels/teams-message-ops.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-message-ops.js","sourceRoot":"","sources":["../../../agent/channels/teams-message-ops.ts"],"names":[],"mappings":"AAAA,mGAAmG;AACnG,oGAAoG;AACpG,mGAAmG;AACnG,iGAAiG;AACjG,mDAAmD;AACnD,EAAE;AACF,iFAAiF;AACjF,4FAA4F;AAC5F,oEAAoE;AACpE,8FAA8F;AAC9F,+FAA+F;AAC/F,4FAA4F;AAC5F,8FAA8F;AAC9F,gGAAgG;AAChG,uCAAuC;AACvC,EAAE;AACF,gGAAgG;AAChG,sFAAsF;AACtF,iGAAiG;AACjG,+FAA+F;AAC/F,oGAAoG;AACpG,oGAAoG;AACpG,gBAAgB;AAChB,EAAE;AACF,kGAAkG;AAClG,mGAAmG;AACnG,kGAAkG;AAClG,2FAA2F;AAG3F,OAAO,EAAE,kBAAkB,EAAE,gBAAgB,EAAoB,MAAM,qBAAqB,CAAC;AAC7F,OAAO,EAAE,oBAAoB,EAAE,MAAM,6BAA6B,CAAC;AACnE,OAAO,EAAE,0BAA0B,EAAE,MAAM,uBAAuB,CAAC;AAEnE;;;;;;;;;GASG;AACH,KAAK,UAAU,sBAAsB,CAAC,SAAiB;IACrD,MAAM,GAAG,GAAG,MAAM,oBAAoB,CAAC,MAAM,0BAA0B,CAAC,SAAS,CAAC,CAAC,CAAC;IACpF,IAAI,CAAC,GAAG,EAAE,CAAC;QACT,MAAM,IAAI,KAAK,CACb,6DAA6D,SAAS,oEAAoE,CAC3I,CAAC;IACJ,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC;AAED,MAAM,CAAC,MAAM,eAAe,GAAsB;IAChD,QAAQ,EAAE,OAAO;IAEjB;iFAC6E;IAC7E,KAAK,CAAC,QAAQ,CAAC,SAAS,EAAE,IAAI,EAAE,IAAI;QAClC,MAAM,EAAE,UAAU,EAAE,cAAc,EAAE,GAAG,MAAM,sBAAsB,CAAC,SAAS,CAAC,CAAC;QAC/E,MAAM,MAAM,GAAgB;YAC1B,QAAQ,EAAE,OAAO;YACjB,UAAU;YACV,cAAc;YACd,GAAG,CAAC,IAAI,EAAE,gBAAgB,CAAC,CAAC,CAAC,EAAE,iBAAiB,EAAE,IAAI,CAAC,gBAAgB,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAChF,CAAC;QACF,OAAO,kBAAkB,CAAC,MAAM,EAAE,IAAI,CAAC,CAAC;IAC1C,CAAC;IAED;;;2EAGuE;IACvE,KAAK,CAAC,WAAW,CAAC,SAAS,EAAE,SAAS,EAAE,IAAI;QAC1C,MAAM,EAAE,UAAU,EAAE,cAAc,EAAE,GAAG,MAAM,sBAAsB,CAAC,SAAS,CAAC,CAAC;QAC/E,MAAM,gBAAgB,CAAC,EAAE,QAAQ,EAAE,OAAO,EAAE,SAAS,EAAE,cAAc,EAAE,UAAU,EAAE,EAAE,SAAS,EAAE,IAAI,CAAC,CAAC;IACxG,CAAC;CACF,CAAC"}

package/dist/agent/channels/teams-origin-codec.d.ts

@@ -0,0 +1,16 @@
+import type { UnifiedWakeOrigin, WakeOriginCodec } from "@open-everywhere/core/agent/adapter-api.js";
+type TeamsOrigin = Extract<UnifiedWakeOrigin, {
+    platform: "teams";
+}>;
+/**
+ * Bot Connector `serviceUrl` host allowlist. The Teams reply POSTs a `client_credentials` bearer
+ * token to `${serviceUrl}/v3/conversations/...`, so the host must be a real Microsoft Bot
+ * Framework endpoint — not merely https. `serviceUrl` rides in off the inbound activity BODY, and
+ * eve's JWT verifier does NOT bind it to the token's `serviceurl` claim, so a scheme-only check
+ * (`startsWith("https://")`) would let a body-supplied `https://evil.example` exfiltrate the
+ * token. Constrain the host to the documented Bot Connector set. Fail-closed on any parse error.
+ */
+export declare function isTrustedTeamsServiceUrl(serviceUrl: unknown): boolean;
+export declare const teamsWakeOriginCodec: WakeOriginCodec<TeamsOrigin>;
+export {};
+//# sourceMappingURL=teams-origin-codec.d.ts.map

package/dist/agent/channels/teams-origin-codec.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-origin-codec.d.ts","sourceRoot":"","sources":["../../../agent/channels/teams-origin-codec.ts"],"names":[],"mappings":"AAkBA,OAAO,KAAK,EAAE,iBAAiB,EAAE,eAAe,EAAE,MAAM,4CAA4C,CAAC;AAErG,KAAK,WAAW,GAAG,OAAO,CAAC,iBAAiB,EAAE;IAAE,QAAQ,EAAE,OAAO,CAAA;CAAE,CAAC,CAAC;AAOrE;;;;;;;GAOG;AACH,wBAAgB,wBAAwB,CAAC,UAAU,EAAE,OAAO,GAAG,OAAO,CAYrE;AA0BD,eAAO,MAAM,oBAAoB,EAAE,eAAe,CAAC,WAAW,CA8B7D,CAAC"}

package/dist/agent/channels/teams-origin-codec.js

@@ -0,0 +1,99 @@
+// The Teams UnifiedWakeOrigin codec + the Bot-Connector serviceUrl host allowlist — MOVED VERBATIM
+// out of core's channels/wake-origin-codecs.ts (OPE-114 stage 4). STORED-DATA COMPATIBILITY IS THE
+// CONTRACT: a Teams origin is JSON-serialised into the durable operational store and fail-closed
+// re-validated on read, so every behaviour here is frozen by core's
+// scripts/wake-origin-fixtures-test.ts (run from the app root with this bundle's boot wiring —
+// scripts/wake-origin-fixtures-boot.ts). Validator tolerances (typeof-only optional checks, extra
+// unknown fields) are LOAD-BEARING for rows already on disk — never tighten them here.
+//
+// The `UnifiedWakeOrigin` TYPE union (including its teams arm) stays in core — it is the wire
+// schema for stored rows; only the codec BEHAVIOUR lives in the bundle, registered by
+// registerTeamsProvider() (../register.ts). `isTrustedTeamsServiceUrl` is exported for the teams
+// post arm (BOTH of its dispatch paths re-validate the serviceUrl before POSTing the Connector
+// token) and applied here on the stored-row `validate` arm — every route by which a serviceUrl can
+// reach a token POST passes it. (There was a third route, the `dmOrigin` DM-delegation-anchor mint
+// arm, which applied the same allowlist; it went with the anchor at OPE-368 — a removed route needs
+// no check.) Core no longer re-exports the predicate (the stale unified-window re-export was removed
+// in stage 4).
+/** COLON-FREE by construction: a task windowId is `[^:]+` (core channels/window-key.ts), so any colon
+ *  in a raw surface id (Teams' `19:...@thread.v2;messageid=` conversation ids) is folded to `_` —
+ *  deterministic, so spawn + ingress still agree on identity. */
+const noColon = (s) => s.replace(/:/g, "_");
+/**
+ * Bot Connector `serviceUrl` host allowlist. The Teams reply POSTs a `client_credentials` bearer
+ * token to `${serviceUrl}/v3/conversations/...`, so the host must be a real Microsoft Bot
+ * Framework endpoint — not merely https. `serviceUrl` rides in off the inbound activity BODY, and
+ * eve's JWT verifier does NOT bind it to the token's `serviceurl` claim, so a scheme-only check
+ * (`startsWith("https://")`) would let a body-supplied `https://evil.example` exfiltrate the
+ * token. Constrain the host to the documented Bot Connector set. Fail-closed on any parse error.
+ */
+export function isTrustedTeamsServiceUrl(serviceUrl) {
+    if (typeof serviceUrl !== "string")
+        return false;
+    let host;
+    try {
+        const u = new URL(serviceUrl);
+        if (u.protocol !== "https:")
+            return false;
+        host = u.hostname.toLowerCase();
+    }
+    catch {
+        return false;
+    }
+    // An entry beginning with "." is a dot-anchored suffix; otherwise an exact host.
+    return teamsServiceHostAllowlist().some((h) => (h.startsWith(".") ? host.endsWith(h) : host === h));
+}
+/** The GLOBAL (commercial) cloud Bot Connector hosts. Sovereign/national clouds use DIFFERENT
+ *  hosts and are NOT in the default (keeping the default minimal, per the no-extrapolation rule):
+ *  a GCC / GCC High / DoD / 21Vianet operator opts theirs in via OE_TEAMS_SERVICE_HOSTS. Verified
+ *  values (Microsoft Learn, "Send proactive messages"): GCC `smba.infra.gcc.teams.microsoft.com`,
+ *  GCC High `smba.infra.gov.teams.microsoft.us`, DoD `smba.infra.dod.teams.microsoft.us`. */
+const DEFAULT_TEAMS_SERVICE_HOSTS = [
+    "smba.trafficmanager.net",
+    ".smba.trafficmanager.net",
+    "botframework.com",
+    ".botframework.com",
+];
+/** The effective serviceUrl host allowlist = the global default PLUS any operator-supplied
+ *  OE_TEAMS_SERVICE_HOSTS (comma-separated; each entry an exact host or a ".suffix"). This is how
+ *  a sovereign-cloud deployment admits its own Bot Connector host without weakening the default —
+ *  the reply's bearer token only ever POSTs to a MATCHED host, all Microsoft-owned. */
+function teamsServiceHostAllowlist() {
+    const extra = (process.env.OE_TEAMS_SERVICE_HOSTS ?? "")
+        .split(",")
+        .map((s) => s.trim().toLowerCase())
+        .filter((s) => s.length > 0);
+    return extra.length > 0 ? [...DEFAULT_TEAMS_SERVICE_HOSTS, ...extra] : DEFAULT_TEAMS_SERVICE_HOSTS;
+}
+export const teamsWakeOriginCodec = {
+    validate: (o) => 
+    // The Bot Connector bearer token is POSTed to serviceUrl, so it must be a Microsoft Bot
+    // Framework host, not merely https (isTrustedTeamsServiceUrl) — the reply path re-validates
+    // regardless, but a bad host must never survive into the map in the first place.
+    isTrustedTeamsServiceUrl(o.serviceUrl) &&
+        typeof o.conversationId === "string" &&
+        o.conversationId.length > 0 &&
+        (o.replyToActivityId === undefined || typeof o.replyToActivityId === "string") &&
+        (o.tenantId === undefined || typeof o.tenantId === "string"),
+    threadRef: (origin) => ({ channelKey: noColon(`teams/${origin.conversationId}`), threadKey: noColon(origin.replyToActivityId ?? origin.conversationId) }),
+    // replyToActivityId present ⇔ the trigger sits in a reply chain (the chain IS the thread);
+    // absent = a plain conversation send.
+    isThreadScoped: (origin) => typeof origin.replyToActivityId === "string" && origin.replyToActivityId.length > 0,
+    containerId: (origin) => origin.conversationId,
+    // A `dmOrigin` arm lived here (OPE-306 seam, landed OPE-315) to mint a DM delegation anchor's reply
+    // origin from the binding's `target` (`serviceUrl` + `conversationId`). OPE-368 deleted the anchor
+    // and the interface member with it — a Teams personal/group chat now diverts into its own
+    // first-class window (OPE-357), so its origin is minted and STORED at dispatch time like every other
+    // wake. NOTHING WEAKENED BY THE REMOVAL: the serviceUrl host allowlist that arm applied at mint is
+    // ALSO applied by `validate` above (every stored row) and again by the post arm before any Connector
+    // token leaves the process, so `isTrustedTeamsServiceUrl` remains on every route to a token POST.
+    //
+    // NO `placementRef` AND NO `carryPlacement`, AND THAT ABSENCE IS THE DECLARATION (OPE-1826). Teams
+    // keeps its placement INSIDE the conversation identity: `threadRef` keys on `replyToActivityId`,
+    // which is the very activity a reply hangs under, so two origins that pass `sameUnifiedConversation`
+    // already agree about where the answer lands and there is no gap for a carry to fill. Declaring an
+    // axis here would be worse than absent — it would make two origins of ONE thread compare unequal on
+    // a field the thread key has already settled. The position is recorded, and held to account against
+    // the live registry, by the `origin-placement-carry` row in core's identity/surface-parity.ts.
+};
+//# sourceMappingURL=teams-origin-codec.js.map

package/dist/agent/channels/teams-origin-codec.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-origin-codec.js","sourceRoot":"","sources":["../../../agent/channels/teams-origin-codec.ts"],"names":[],"mappings":"AAAA,mGAAmG;AACnG,mGAAmG;AACnG,iGAAiG;AACjG,oEAAoE;AACpE,+FAA+F;AAC/F,kGAAkG;AAClG,uFAAuF;AACvF,EAAE;AACF,8FAA8F;AAC9F,sFAAsF;AACtF,iGAAiG;AACjG,+FAA+F;AAC/F,mGAAmG;AACnG,mGAAmG;AACnG,oGAAoG;AACpG,qGAAqG;AACrG,eAAe;AAMf;;iEAEiE;AACjE,MAAM,OAAO,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,IAAI,EAAE,GAAG,CAAC,CAAC;AAE5D;;;;;;;GAOG;AACH,MAAM,UAAU,wBAAwB,CAAC,UAAmB;IAC1D,IAAI,OAAO,UAAU,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC;IACjD,IAAI,IAAY,CAAC;IACjB,IAAI,CAAC;QACH,MAAM,CAAC,GAAG,IAAI,GAAG,CAAC,UAAU,CAAC,CAAC;QAC9B,IAAI,CAAC,CAAC,QAAQ,KAAK,QAAQ;YAAE,OAAO,KAAK,CAAC;QAC1C,IAAI,GAAG,CAAC,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC;IAClC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;IACD,iFAAiF;IACjF,OAAO,yBAAyB,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,CAAC,CAAC;AACtG,CAAC;AAED;;;;6FAI6F;AAC7F,MAAM,2BAA2B,GAAsB;IACrD,yBAAyB;IACzB,0BAA0B;IAC1B,kBAAkB;IAClB,mBAAmB;CACpB,CAAC;AAEF;;;uFAGuF;AACvF,SAAS,yBAAyB;IAChC,MAAM,KAAK,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,sBAAsB,IAAI,EAAE,CAAC;SACrD,KAAK,CAAC,GAAG,CAAC;SACV,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;SAClC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC;IAC/B,OAAO,KAAK,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,2BAA2B,EAAE,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC,2BAA2B,CAAC;AACrG,CAAC;AAED,MAAM,CAAC,MAAM,oBAAoB,GAAiC;IAChE,QAAQ,EAAE,CAAC,CAAC,EAAE,EAAE;IACd,wFAAwF;IACxF,4FAA4F;IAC5F,iFAAiF;IACjF,wBAAwB,CAAC,CAAC,CAAC,UAAU,CAAC;QACtC,OAAO,CAAC,CAAC,cAAc,KAAK,QAAQ;QACpC,CAAC,CAAC,cAAc,CAAC,MAAM,GAAG,CAAC;QAC3B,CAAC,CAAC,CAAC,iBAAiB,KAAK,SAAS,IAAI,OAAO,CAAC,CAAC,iBAAiB,KAAK,QAAQ,CAAC;QAC9E,CAAC,CAAC,CAAC,QAAQ,KAAK,SAAS,IAAI,OAAO,CAAC,CAAC,QAAQ,KAAK,QAAQ,CAAC;IAC9D,SAAS,EAAE,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,EAAE,UAAU,EAAE,OAAO,CAAC,SAAS,MAAM,CAAC,cAAc,EAAE,CAAC,EAAE,SAAS,EAAE,OAAO,CAAC,MAAM,CAAC,iBAAiB,IAAI,MAAM,CAAC,cAAc,CAAC,EAAE,CAAC;IACzJ,2FAA2F;IAC3F,sCAAsC;IACtC,cAAc,EAAE,CAAC,MAAM,EAAE,EAAE,CAAC,OAAO,MAAM,CAAC,iBAAiB,KAAK,QAAQ,IAAI,MAAM,CAAC,iBAAiB,CAAC,MAAM,GAAG,CAAC;IAC/G,WAAW,EAAE,CAAC,MAAM,EAAE,EAAE,CAAC,MAAM,CAAC,cAAc;IAC9C,oGAAoG;IACpG,mGAAmG;IACnG,0FAA0F;IAC1F,qGAAqG;IACrG,mGAAmG;IACnG,qGAAqG;IACrG,kGAAkG;IAClG,EAAE;IACF,mGAAmG;IACnG,iGAAiG;IACjG,qGAAqG;IACrG,mGAAmG;IACnG,oGAAoG;IACpG,oGAAoG;IACpG,+FAA+F;CAChG,CAAC"}

package/dist/agent/channels/teams-post-arm.d.ts

@@ -0,0 +1,37 @@
+import type { PostArm, ReplyTarget, EditLocus } from "@open-everywhere/core/agent/adapter-api.js";
+/** Exported for `teams-message-ops.ts` (OPE-899) — the SurfaceMessageOps registration reuses this
+ *  exact shape (serviceUrl + conversationId + an optional reply anchor) rather than inventing a
+ *  second one; see `dispatchTeamsReply`'s own export note. */
+export type TeamsTarget = Extract<ReplyTarget, {
+    platform: "teams";
+}>;
+/** MID-TURN: a Bot-Framework message activity into the captured conversation reference. eve mints the
+ *  Connector token from MICROSOFT_APP_ID/PASSWORD; check the id for an honest early error. Thread onto
+ *  the trigger's root activity when the caller resolved one (a channel/group reply chains via
+ *  replyToTeamsActivity — eve's exact reply semantics, matching the unified arm and channel.thread.post);
+ *  a plain conversation send otherwise (personal chats, or no root id). */
+/** Exported (OPE-899) so `teams-message-ops.ts`'s SurfaceMessageOps `postText` can post through the
+ *  SAME transport this mid-turn reply arm uses, rather than a second copy of the Connector send.
+ *  That module resolves its own `TeamsTarget` from the `conversation`-grain address store
+ *  (`teams-conversation-ref.ts`, OPE-899) instead of from a live binding, but the target shape and
+ *  every refusal below are identical either way. */
+export declare function dispatchTeamsReply(target: TeamsTarget, text: string): Promise<string>;
+/**
+ * EDIT (OPE-793): rewrite one of our own posted activities via eve's `updateTeamsActivity` (the Bot
+ * Framework update-activity call), on the SAME transport and credentials the post arms use. The
+ * Teams client shows an "Edited" marker on the activity, so the change is visible in the room.
+ *
+ * THE SAME TRUSTED-HOST ALLOWLIST BOTH POST ARMS APPLY. This call POSTs a client_credentials
+ * Connector bearer token to `locus.serviceUrl`, so it must be a Bot Framework host — the identical
+ * check, for the identical reason, and its absence here would be the OPE-315 gap re-opened on a new
+ * route. The serviceUrl reaches this arm from the session binding or the frozen wake origin (never
+ * model input), and it is re-validated anyway.
+ *
+ * NO SPLIT, like the Discord arm: one activity is one activity, so text past Teams' own cap is
+ * refused rather than truncated. Ownership was decided upstream against the own-post ledger.
+ */
+/** Exported (OPE-899) so `teams-message-ops.ts`'s SurfaceMessageOps `editMessage` reuses this SAME
+ *  update-activity transport rather than a second copy of it. */
+export declare function editTeamsMessage(locus: EditLocus, messageId: string, text: string): Promise<void>;
+export declare const teamsPostArm: PostArm;
+//# sourceMappingURL=teams-post-arm.d.ts.map

package/dist/agent/channels/teams-post-arm.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-post-arm.d.ts","sourceRoot":"","sources":["../../../agent/channels/teams-post-arm.ts"],"names":[],"mappings":"AA+BA,OAAO,KAAK,EACV,OAAO,EAEP,WAAW,EAGX,SAAS,EAGV,MAAM,4CAA4C,CAAC;AAEpD;;8DAE8D;AAC9D,MAAM,MAAM,WAAW,GAAG,OAAO,CAAC,WAAW,EAAE;IAAE,QAAQ,EAAE,OAAO,CAAA;CAAE,CAAC,CAAC;AAGtE;;;;2EAI2E;AAC3E;;;;oDAIoD;AACpD,wBAAsB,kBAAkB,CAAC,MAAM,EAAE,WAAW,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CA6B3F;AA2CD;;;;;;;;;;;;;GAaG;AACH;iEACiE;AACjE,wBAAsB,gBAAgB,CAAC,KAAK,EAAE,SAAS,EAAE,SAAS,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAmCvG;AA8HD,eAAO,MAAM,YAAY,EAAE,OAe1B,CAAC"}

package/dist/agent/channels/teams-post-arm.js

@@ -0,0 +1,280 @@
+// teams-post-arm — Teams's POST arm for the post-arms registry (OPE-114 stage 1c). Absorbs, VERBATIM,
+// Teams's arms out of the three reply/delivery spines: reply-post.ts (resolveReplyTarget's teams case
+// + dispatchReply's send/reply branch + the teams splitTeamsMessageText chunking used by
+// postTerminalProse), unified-reply.ts (liveTeamsPost, incl. the trusted-serviceUrl re-validation),
+// and unified-redrive.ts (the teams describe/container cases). The transport is eve's own Bot-Framework
+// Connector token (minted from MICROSOFT_APP_ID/PASSWORD) over a HOST-SIDE Connector fetch — see
+// teams-connector.ts's header for why the send/reply/update calls are no longer eve's own
+// `sendTeamsActivity`/`replyToTeamsActivity`/`updateTeamsActivity` (OPE-1237: eve's own transport
+// throws away the response headers, so there is no way to honour a 429's `Retry-After` by wrapping
+// its return value).
+//
+// ONE DELIBERATE DIVERGENCE FROM "VERBATIM" (OPE-315): dispatchTeamsReply now applies the
+// isTrustedTeamsServiceUrl host allowlist its unified sibling always did. That was a real gap, not a
+// stylistic one — see the check's own comment.
+import { resolveTeamsAppId, splitTeamsMessageText, TEAMS_MESSAGE_TEXT_MAX_LENGTH } from "eve/channels/teams";
+import { teamsConnectorWrite, sendTeamsActivityBackedOff, replyToTeamsActivityBackedOff, updateTeamsActivityBackedOff, } from "./teams-connector.js";
+import { isTrustedTeamsServiceUrl } from "./teams-origin-codec.js";
+import { teamsPersonalConversationRef, teamsSoleTenantRegion, rememberTeamsPersonalConversation, } from "./teams-conversation-ref.js";
+import { restoreTeamsPersonId } from "./teams-id-restore.js";
+import { markNotApplied, carryFailureSignals } from "@open-everywhere/core/agent/adapter-api.js";
+/** MID-TURN: a Bot-Framework message activity into the captured conversation reference. eve mints the
+ *  Connector token from MICROSOFT_APP_ID/PASSWORD; check the id for an honest early error. Thread onto
+ *  the trigger's root activity when the caller resolved one (a channel/group reply chains via
+ *  replyToTeamsActivity — eve's exact reply semantics, matching the unified arm and channel.thread.post);
+ *  a plain conversation send otherwise (personal chats, or no root id). */
+/** Exported (OPE-899) so `teams-message-ops.ts`'s SurfaceMessageOps `postText` can post through the
+ *  SAME transport this mid-turn reply arm uses, rather than a second copy of the Connector send.
+ *  That module resolves its own `TeamsTarget` from the `conversation`-grain address store
+ *  (`teams-conversation-ref.ts`, OPE-899) instead of from a live binding, but the target shape and
+ *  every refusal below are identical either way. */
+export async function dispatchTeamsReply(target, text) {
+    // Both pre-flight refusals are DEFINITIVE (OPE-821): the call never leaves this host, so nothing
+    // reached the room and the post spine may release its dedupe claim for an identical retry.
+    if (!process.env.MICROSOFT_APP_ID && !process.env.TEAMS_APP_ID) {
+        throw markNotApplied(new Error("reply couldn't post to Teams — MICROSOFT_APP_ID is not set."));
+    }
+    // 🔴 THE SAME HOST ALLOWLIST THE UNIFIED ARM APPLIES (OPE-315). This path POSTs a client_credentials
+    // Connector bearer token to `target.serviceUrl`, and until now it was the ONE serviceUrl route with
+    // no host check: the stored-origin path is gated by the codec validator (teams-origin-codec.ts) and
+    // re-gated in liveTeamsPost, but a mid-turn target is assembled by resolveTarget from binding
+    // attributes with only a non-empty test. Narrow (it takes a rogue Bot Framework channel on the same
+    // bot registration to place an attacker host there) but the same class as the unified arm's, and
+    // the fix is three lines. Token-free error, mirroring liveTeamsPost's.
+    if (!isTrustedTeamsServiceUrl(target.serviceUrl)) {
+        throw markNotApplied(new Error(`reply couldn't post to Teams — serviceUrl is not a Bot Framework host (conversation ${target.conversationId})`));
+    }
+    const res = target.replyToActivityId
+        ? await replyToTeamsActivityBackedOff({
+            serviceUrl: target.serviceUrl,
+            conversationId: target.conversationId,
+            activityId: target.replyToActivityId,
+            body: { type: "message", text },
+        })
+        : await sendTeamsActivityBackedOff({
+            serviceUrl: target.serviceUrl,
+            conversationId: target.conversationId,
+            body: { type: "message", text },
+        });
+    return res.id;
+}
+/** UNIFIED: a Bot-Framework message activity into the frozen conversation reference — the SAME
+ *  transport + env credentials the mid-turn reply arm uses. Anchored into the reply CHAIN via
+ *  replyToTeamsActivity when the origin froze a thread-root activity id (teamsThreadRootActivityId),
+ *  else a plain conversation send. Every target field rides the host-frozen wake origin, never the
+ *  model. */
+async function liveTeamsPost(origin, text) {
+    if (!process.env.MICROSOFT_APP_ID && !process.env.TEAMS_APP_ID) {
+        // DEFINITIVE, like the mid-turn arm's pre-flights: nothing left this host.
+        throw markNotApplied(new Error(`unified reply couldn't post to Teams — MICROSOFT_APP_ID is not set (conversation ${origin.conversationId})`));
+    }
+    // Belt-and-braces re-validation (isUnifiedWakeOrigin already enforces it): the Connector bearer
+    // token is POSTed to this host, so it must be a Microsoft Bot Framework endpoint — a scheme-only
+    // https check would let a body-supplied serviceUrl exfiltrate the token.
+    if (!isTrustedTeamsServiceUrl(origin.serviceUrl)) {
+        throw markNotApplied(new Error(`unified reply couldn't post to Teams — serviceUrl is not a Bot Framework host (conversation ${origin.conversationId})`));
+    }
+    let id;
+    try {
+        const res = origin.replyToActivityId
+            ? await replyToTeamsActivityBackedOff({
+                serviceUrl: origin.serviceUrl,
+                conversationId: origin.conversationId,
+                activityId: origin.replyToActivityId,
+                body: { type: "message", text },
+            })
+            : await sendTeamsActivityBackedOff({
+                serviceUrl: origin.serviceUrl,
+                conversationId: origin.conversationId,
+                body: { type: "message", text },
+            });
+        id = res.id;
+    }
+    catch (err) {
+        // Token-free error: never echo the transport error body (defensive parity with the other arms).
+        // AMBIGUOUS unless the Connector gave a status to say otherwise (OPE-821) — a send whose answer
+        // never arrived may still have reached the room, so the class carries over rather than being
+        // dropped by the re-wrap. A number is the only thing carried; no body, no URL, no token.
+        throw carryFailureSignals(err, new Error(`unified reply couldn't post to Teams — the Connector post failed (conversation ${origin.conversationId})`));
+    }
+    return id || "unknown";
+}
+/**
+ * EDIT (OPE-793): rewrite one of our own posted activities via eve's `updateTeamsActivity` (the Bot
+ * Framework update-activity call), on the SAME transport and credentials the post arms use. The
+ * Teams client shows an "Edited" marker on the activity, so the change is visible in the room.
+ *
+ * THE SAME TRUSTED-HOST ALLOWLIST BOTH POST ARMS APPLY. This call POSTs a client_credentials
+ * Connector bearer token to `locus.serviceUrl`, so it must be a Bot Framework host — the identical
+ * check, for the identical reason, and its absence here would be the OPE-315 gap re-opened on a new
+ * route. The serviceUrl reaches this arm from the session binding or the frozen wake origin (never
+ * model input), and it is re-validated anyway.
+ *
+ * NO SPLIT, like the Discord arm: one activity is one activity, so text past Teams' own cap is
+ * refused rather than truncated. Ownership was decided upstream against the own-post ledger.
+ */
+/** Exported (OPE-899) so `teams-message-ops.ts`'s SurfaceMessageOps `editMessage` reuses this SAME
+ *  update-activity transport rather than a second copy of it. */
+export async function editTeamsMessage(locus, messageId, text) {
+    // The three pre-flight refusals are DEFINITIVE (OPE-802): the call never leaves this host, so the
+    // message cannot have changed and a fresh `reply` is the right remedy. The Connector failure below
+    // is not — a failed update may still have applied — so it stays unmarked and fails closed.
+    if (!process.env.MICROSOFT_APP_ID && !process.env.TEAMS_APP_ID) {
+        throw markNotApplied(new Error("edit_reply couldn't update the Teams message — MICROSOFT_APP_ID is not set."));
+    }
+    if (!locus.serviceUrl || !isTrustedTeamsServiceUrl(locus.serviceUrl)) {
+        throw markNotApplied(new Error(`edit_reply couldn't update the Teams message — serviceUrl is not a Bot Framework host (conversation ${locus.channelId})`));
+    }
+    if (text.length > TEAMS_MESSAGE_TEXT_MAX_LENGTH) {
+        throw markNotApplied(new Error(`edit_reply couldn't update the Teams message — the new text is ${text.length} characters and Teams caps one message at ${TEAMS_MESSAGE_TEXT_MAX_LENGTH}. An edit cannot split a message; shorten it, or post a new reply.`));
+    }
+    try {
+        await updateTeamsActivityBackedOff({
+            serviceUrl: locus.serviceUrl,
+            conversationId: locus.channelId,
+            activityId: messageId,
+            body: { type: "message", text },
+        });
+    }
+    catch (err) {
+        // Token-free error, matching both post arms: never echo the transport error body. `err` may now
+        // be the NAMED `RateLimitExhaustedError` (OPE-1237) rather than an ordinary Connector throw —
+        // `carryFailureSignals` copies its `status` (429, always AMBIGUOUS per platform-failure.ts) onto
+        // the wrapped error, the same treatment `liveTeamsPost`'s catch below gives it. That keeps the
+        // 429 case failing closed exactly as an unclassified Connector failure already did — this stays
+        // an improvement in what a caller reading `.status` can tell, never a behaviour change.
+        throw carryFailureSignals(err, new Error(`edit_reply couldn't update the Teams message — the Connector update failed (conversation ${locus.channelId})`));
+    }
+}
+/** Teams' own pre-flight: without an app id nothing can mint a Connector token. DEFINITIVE — the
+ *  call never leaves this host — so the caller may retry an identical send once the id is set. */
+function requireTeamsAppCredential(what) {
+    if (!process.env.MICROSOFT_APP_ID && !process.env.TEAMS_APP_ID) {
+        throw markNotApplied(new Error(`${what} couldn't reach Teams — MICROSOFT_APP_ID is not set.`));
+    }
+}
+/**
+ * Open (or re-open) the 1:1 chat between the bot and one person — `POST {serviceUrl}/v3/conversations`
+ * with the bot, the member and the tenant.
+ *
+ * IT IS THE ONLY WAY TO COLD-ADDRESS A TEAMS PERSON, and it is why OPE-887 exists: the Bot Framework
+ * has no `conversations.open` keyed on a bare user id, so the deployment must already know a REGION
+ * (`serviceUrl`) and a TENANT before it can ask. Both come from the proactive-address table
+ * (channels/teams-conversation-ref.ts), captured off real inbound activities.
+ *
+ * The create is IDEMPOTENT for a one-member, non-group conversation: Microsoft documents it as
+ * returning the EXISTING 1:1 chat rather than minting a second one. That is a documented fact and not
+ * a measured one — if it turned out to be false, the visible symptom would be a duplicate chat, never
+ * a lost message, and the stored reference below means the call happens at most once per person
+ * anyway.
+ *
+ * 🔴 THE REFUSAL THIS ARM MUST STAY HONEST ABOUT: Microsoft refuses the create when the Teams app is
+ * not installed for that person in the PERSONAL scope. So a Teams DM arm reaches the people who have
+ * the app, and NOT the whole tenant. The error names that, because "the message did not send" without
+ * the reason sends a caller looking in the wrong place.
+ */
+async function openTeamsPersonalConversation(region, principalId) {
+    const appId = await resolveTeamsAppId();
+    const res = await teamsConnectorWrite({
+        operation: "conversations.create",
+        serviceUrl: region.serviceUrl,
+        path: "/v3/conversations",
+        method: "POST",
+        body: {
+            isGroup: false,
+            bot: { id: `28:${appId}` },
+            members: [{ id: principalId }],
+            channelData: { tenant: { id: region.tenantId } },
+            tenantId: region.tenantId,
+        },
+    });
+    const id = res.ok && res.body && typeof res.body === "object" ? res.body.id : undefined;
+    if (typeof id !== "string" || id.length === 0) {
+        // Token-free, and never the Connector's own body: the response can echo request material.
+        throw new Error(`couldn't open a Teams 1:1 chat with that account (Bot Framework answered ${res.status}). Microsoft refuses this when the Teams app is not installed for that person in the personal scope.`);
+    }
+    return id;
+}
+/**
+ * DM (OPE-887): deliver `text` to one person's 1:1 Teams chat. The THIRD provider to implement this
+ * member, after Slack and Discord, and the one whose transport needed a durable seam first.
+ *
+ * WHAT IT COSTS TO GET HERE, in one paragraph. `DirectMessageRequest` names WHO and never WHERE, which
+ * is right and which Slack and Discord satisfy from a bot token alone. Teams cannot: a send needs a
+ * regional `serviceUrl` and a Microsoft-minted conversation id, and neither is derivable from a person
+ * id. So the deployment captures both off inbound activities (channels/teams-conversation-ref.ts) and
+ * this arm reads them back. The caller's contract is unchanged.
+ *
+ * THREE OUTCOMES, and each is a real answer:
+ *   1. a 1:1 reference is stored ⇒ one send.
+ *   2. no 1:1 reference, but this deployment knows exactly one tenant and its region ⇒ open the chat,
+ *      remember it, send.
+ *   3. neither ⇒ REFUSE, loudly and token-free. That is not a defect to paper over: this deployment
+ *      genuinely has no address for that person, and a silent no-op would leave a consent ask
+ *      apparently sent and actually nowhere.
+ *
+ * `actions` ARE IGNORED, deliberately and per the registry's "undefined = unsupported, never faked":
+ * this arm posts a plain message activity, and a Teams button would need an Adaptive Card plus an
+ * invoke route to receive the tap. Core's copy always stands on its own without a button
+ * ({@link DirectMessageAction}'s own rule), so the text delivered here is complete.
+ */
+async function deliverTeamsDirectMessage(input) {
+    requireTeamsAppCredential("the direct message");
+    // 🔴 RESTORE THE RAW `29:` ID ONCE, HERE, BEFORE ANY USE (OPE-1078). A granted `teams:person/<id>`
+    // address carries the SURFACE-KEY spelling — the only one the resource-grant grammar admits — and
+    // every use below needs the raw Bot Framework id: the stored-reference lookup keys on it, and
+    // `openTeamsPersonalConversation` puts it in the Connector's `members` list, where a wrong spelling
+    // is a refused create rather than a delivered message. A caller that already holds the raw id (the
+    // recipient's own binding) is answered unchanged and pays no store read.
+    const principalId = await restoreTeamsPersonId(input.principalId.trim());
+    if (principalId.length === 0)
+        throw markNotApplied(new Error("the direct message couldn't reach Teams — no account id was given."));
+    const stored = await teamsPersonalConversationRef(principalId);
+    let ref;
+    if (stored) {
+        ref = stored;
+    }
+    else {
+        const region = await teamsSoleTenantRegion();
+        if (!region) {
+            // DEFINITIVE: nothing left this host. Naming the two ways an address is acquired is what lets an
+            // operator act — the alternative is a message that never arrives and no reason why.
+            throw markNotApplied(new Error("the direct message couldn't reach Teams — this deployment holds no Bot Framework conversation reference for that account, and no single Teams tenant it could open one in. A reference is captured when the person messages the bot, or when the bot sees a channel in exactly one tenant."));
+        }
+        ref = { ...region, conversationId: await openTeamsPersonalConversation(region, principalId) };
+        // Best-effort: a failed write costs a repeated create next time, never a failed send.
+        await rememberTeamsPersonalConversation(principalId, ref);
+    }
+    // READ-TIME allowlist, for the same reason every other Teams write applies one: this POSTs a
+    // Connector bearer token to the host. The stored reference was checked on the way in too.
+    if (!isTrustedTeamsServiceUrl(ref.serviceUrl)) {
+        throw markNotApplied(new Error("the direct message couldn't reach Teams — the stored serviceUrl is not a Bot Framework host."));
+    }
+    // Teams caps one activity, so a long notice is split exactly as every other Teams post is; the
+    // FIRST part's id is the returned anchor, matching the Discord arm.
+    const parts = splitTeamsMessageText(input.text);
+    let messageId = "";
+    for (const part of parts) {
+        const res = await sendTeamsActivityBackedOff({ serviceUrl: ref.serviceUrl, conversationId: ref.conversationId, body: { type: "message", text: part } });
+        if (messageId.length === 0)
+            messageId = res.id;
+    }
+    return { surfaceId: ref.conversationId, messageId: messageId || "unknown" };
+}
+export const teamsPostArm = {
+    platform: "teams",
+    resolveTarget: (bag) => {
+        // Proactive Teams sends need the Bot-Framework conversation reference (serviceUrl + conversation
+        // id) the inbound turn captured — you cannot cold-address a Teams chat.
+        const serviceUrl = bag.str("serviceUrl");
+        const conversationId = bag.str("conversationId");
+        return serviceUrl && conversationId ? { platform: "teams", serviceUrl, conversationId } : null;
+    },
+    dispatchReply: (target, text) => dispatchTeamsReply(target, text),
+    dispatchUnified: (origin, text, deps) => (deps.postTeams ?? liveTeamsPost)(origin, text),
+    describeRedriveTarget: (origin) => `teams conversation ${origin.conversationId}`,
+    redriveContainerId: (origin) => origin.conversationId,
+    editMessage: editTeamsMessage,
+    deliverDirectMessage: deliverTeamsDirectMessage,
+};
+//# sourceMappingURL=teams-post-arm.js.map

package/dist/agent/channels/teams-post-arm.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-post-arm.js","sourceRoot":"","sources":["../../../agent/channels/teams-post-arm.ts"],"names":[],"mappings":"AAAA,sGAAsG;AACtG,sGAAsG;AACtG,yFAAyF;AACzF,oGAAoG;AACpG,wGAAwG;AACxG,iGAAiG;AACjG,0FAA0F;AAC1F,kGAAkG;AAClG,mGAAmG;AACnG,qBAAqB;AACrB,EAAE;AACF,0FAA0F;AAC1F,qGAAqG;AACrG,+CAA+C;AAE/C,OAAO,EAAE,iBAAiB,EAAE,qBAAqB,EAAE,6BAA6B,EAAE,MAAM,oBAAoB,CAAC;AAC7G,OAAO,EACL,mBAAmB,EACnB,0BAA0B,EAC1B,6BAA6B,EAC7B,4BAA4B,GAC7B,MAAM,sBAAsB,CAAC;AAC9B,OAAO,EAAE,wBAAwB,EAAE,MAAM,yBAAyB,CAAC;AACnE,OAAO,EACL,4BAA4B,EAC5B,qBAAqB,EACrB,iCAAiC,GAElC,MAAM,6BAA6B,CAAC;AACrC,OAAO,EAAE,oBAAoB,EAAE,MAAM,uBAAuB,CAAC;AAC7D,OAAO,EAAE,cAAc,EAAE,mBAAmB,EAAE,MAAM,4CAA4C,CAAC;AAkBjG;;;;2EAI2E;AAC3E;;;;oDAIoD;AACpD,MAAM,CAAC,KAAK,UAAU,kBAAkB,CAAC,MAAmB,EAAE,IAAY;IACxE,iGAAiG;IACjG,2FAA2F;IAC3F,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,gBAAgB,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,YAAY,EAAE,CAAC;QAC/D,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,6DAA6D,CAAC,CAAC,CAAC;IACjG,CAAC;IACD,qGAAqG;IACrG,oGAAoG;IACpG,oGAAoG;IACpG,8FAA8F;IAC9F,oGAAoG;IACpG,iGAAiG;IACjG,uEAAuE;IACvE,IAAI,CAAC,wBAAwB,CAAC,MAAM,CAAC,UAAU,CAAC,EAAE,CAAC;QACjD,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,uFAAuF,MAAM,CAAC,cAAc,GAAG,CAAC,CAAC,CAAC;IACnJ,CAAC;IACD,MAAM,GAAG,GAAG,MAAM,CAAC,iBAAiB;QAClC,CAAC,CAAC,MAAM,6BAA6B,CAAC;YAClC,UAAU,EAAE,MAAM,CAAC,UAAU;YAC7B,cAAc,EAAE,MAAM,CAAC,cAAc;YACrC,UAAU,EAAE,MAAM,CAAC,iBAAiB;YACpC,IAAI,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE;SAChC,CAAC;QACJ,CAAC,CAAC,MAAM,0BAA0B,CAAC;YAC/B,UAAU,EAAE,MAAM,CAAC,UAAU;YAC7B,cAAc,EAAE,MAAM,CAAC,cAAc;YACrC,IAAI,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE;SAChC,CAAC,CAAC;IACP,OAAO,GAAG,CAAC,EAAE,CAAC;AAChB,CAAC;AAED;;;;aAIa;AACb,KAAK,UAAU,aAAa,CAAC,MAAmB,EAAE,IAAY;IAC5D,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,gBAAgB,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,YAAY,EAAE,CAAC;QAC/D,2EAA2E;QAC3E,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,oFAAoF,MAAM,CAAC,cAAc,GAAG,CAAC,CAAC,CAAC;IAChJ,CAAC;IACD,gGAAgG;IAChG,iGAAiG;IACjG,yEAAyE;IACzE,IAAI,CAAC,wBAAwB,CAAC,MAAM,CAAC,UAAU,CAAC,EAAE,CAAC;QACjD,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,+FAA+F,MAAM,CAAC,cAAc,GAAG,CAAC,CAAC,CAAC;IAC3J,CAAC;IACD,IAAI,EAAU,CAAC;IACf,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,MAAM,CAAC,iBAAiB;YAClC,CAAC,CAAC,MAAM,6BAA6B,CAAC;gBAClC,UAAU,EAAE,MAAM,CAAC,UAAU;gBAC7B,cAAc,EAAE,MAAM,CAAC,cAAc;gBACrC,UAAU,EAAE,MAAM,CAAC,iBAAiB;gBACpC,IAAI,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE;aAChC,CAAC;YACJ,CAAC,CAAC,MAAM,0BAA0B,CAAC;gBAC/B,UAAU,EAAE,MAAM,CAAC,UAAU;gBAC7B,cAAc,EAAE,MAAM,CAAC,cAAc;gBACrC,IAAI,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE;aAChC,CAAC,CAAC;QACP,EAAE,GAAG,GAAG,CAAC,EAAE,CAAC;IACd,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,gGAAgG;QAChG,gGAAgG;QAChG,6FAA6F;QAC7F,yFAAyF;QACzF,MAAM,mBAAmB,CAAC,GAAG,EAAE,IAAI,KAAK,CAAC,kFAAkF,MAAM,CAAC,cAAc,GAAG,CAAC,CAAC,CAAC;IACxJ,CAAC;IACD,OAAO,EAAE,IAAI,SAAS,CAAC;AACzB,CAAC;AAED;;;;;;;;;;;;;GAaG;AACH;iEACiE;AACjE,MAAM,CAAC,KAAK,UAAU,gBAAgB,CAAC,KAAgB,EAAE,SAAiB,EAAE,IAAY;IACtF,kGAAkG;IAClG,mGAAmG;IACnG,2FAA2F;IAC3F,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,gBAAgB,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,YAAY,EAAE,CAAC;QAC/D,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,6EAA6E,CAAC,CAAC,CAAC;IACjH,CAAC;IACD,IAAI,CAAC,KAAK,CAAC,UAAU,IAAI,CAAC,wBAAwB,CAAC,KAAK,CAAC,UAAU,CAAC,EAAE,CAAC;QACrE,MAAM,cAAc,CAClB,IAAI,KAAK,CAAC,uGAAuG,KAAK,CAAC,SAAS,GAAG,CAAC,CACrI,CAAC;IACJ,CAAC;IACD,IAAI,IAAI,CAAC,MAAM,GAAG,6BAA6B,EAAE,CAAC;QAChD,MAAM,cAAc,CAClB,IAAI,KAAK,CACP,kEAAkE,IAAI,CAAC,MAAM,6CAA6C,6BAA6B,oEAAoE,CAC5N,CACF,CAAC;IACJ,CAAC;IACD,IAAI,CAAC;QACH,MAAM,4BAA4B,CAAC;YACjC,UAAU,EAAE,KAAK,CAAC,UAAU;YAC5B,cAAc,EAAE,KAAK,CAAC,SAAS;YAC/B,UAAU,EAAE,SAAS;YACrB,IAAI,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE;SAChC,CAAC,CAAC;IACL,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,gGAAgG;QAChG,8FAA8F;QAC9F,iGAAiG;QACjG,+FAA+F;QAC/F,gGAAgG;QAChG,wFAAwF;QACxF,MAAM,mBAAmB,CAAC,GAAG,EAAE,IAAI,KAAK,CAAC,4FAA4F,KAAK,CAAC,SAAS,GAAG,CAAC,CAAC,CAAC;IAC5J,CAAC;AACH,CAAC;AAED;kGACkG;AAClG,SAAS,yBAAyB,CAAC,IAAY;IAC7C,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,gBAAgB,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,YAAY,EAAE,CAAC;QAC/D,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,GAAG,IAAI,sDAAsD,CAAC,CAAC,CAAC;IACjG,CAAC;AACH,CAAC;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,KAAK,UAAU,6BAA6B,CAAC,MAAkE,EAAE,WAAmB;IAClI,MAAM,KAAK,GAAG,MAAM,iBAAiB,EAAE,CAAC;IACxC,MAAM,GAAG,GAAG,MAAM,mBAAmB,CAAC;QACpC,SAAS,EAAE,sBAAsB;QACjC,UAAU,EAAE,MAAM,CAAC,UAAU;QAC7B,IAAI,EAAE,mBAAmB;QACzB,MAAM,EAAE,MAAM;QACd,IAAI,EAAE;YACJ,OAAO,EAAE,KAAK;YACd,GAAG,EAAE,EAAE,EAAE,EAAE,MAAM,KAAK,EAAE,EAAE;YAC1B,OAAO,EAAE,CAAC,EAAE,EAAE,EAAE,WAAW,EAAE,CAAC;YAC9B,WAAW,EAAE,EAAE,MAAM,EAAE,EAAE,EAAE,EAAE,MAAM,CAAC,QAAQ,EAAE,EAAE;YAChD,QAAQ,EAAE,MAAM,CAAC,QAAQ;SAC1B;KACF,CAAC,CAAC;IACH,MAAM,EAAE,GAAG,GAAG,CAAC,EAAE,IAAI,GAAG,CAAC,IAAI,IAAI,OAAO,GAAG,CAAC,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAE,GAAG,CAAC,IAAyB,CAAC,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC;IAC9G,IAAI,OAAO,EAAE,KAAK,QAAQ,IAAI,EAAE,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC9C,0FAA0F;QAC1F,MAAM,IAAI,KAAK,CACb,4EAA4E,GAAG,CAAC,MAAM,sGAAsG,CAC7L,CAAC;IACJ,CAAC;IACD,OAAO,EAAE,CAAC;AACZ,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,KAAK,UAAU,yBAAyB,CAAC,KAA2B;IAClE,yBAAyB,CAAC,oBAAoB,CAAC,CAAC;IAChD,mGAAmG;IACnG,kGAAkG;IAClG,8FAA8F;IAC9F,oGAAoG;IACpG,mGAAmG;IACnG,yEAAyE;IACzE,MAAM,WAAW,GAAG,MAAM,oBAAoB,CAAC,KAAK,CAAC,WAAW,CAAC,IAAI,EAAE,CAAC,CAAC;IACzE,IAAI,WAAW,CAAC,MAAM,KAAK,CAAC;QAAE,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,oEAAoE,CAAC,CAAC,CAAC;IAEpI,MAAM,MAAM,GAAG,MAAM,4BAA4B,CAAC,WAAW,CAAC,CAAC;IAC/D,IAAI,GAAyB,CAAC;IAC9B,IAAI,MAAM,EAAE,CAAC;QACX,GAAG,GAAG,MAAM,CAAC;IACf,CAAC;SAAM,CAAC;QACN,MAAM,MAAM,GAAG,MAAM,qBAAqB,EAAE,CAAC;QAC7C,IAAI,CAAC,MAAM,EAAE,CAAC;YACZ,iGAAiG;YACjG,oFAAoF;YACpF,MAAM,cAAc,CAClB,IAAI,KAAK,CACP,4RAA4R,CAC7R,CACF,CAAC;QACJ,CAAC;QACD,GAAG,GAAG,EAAE,GAAG,MAAM,EAAE,cAAc,EAAE,MAAM,6BAA6B,CAAC,MAAM,EAAE,WAAW,CAAC,EAAE,CAAC;QAC9F,sFAAsF;QACtF,MAAM,iCAAiC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC;IAC5D,CAAC;IAED,6FAA6F;IAC7F,0FAA0F;IAC1F,IAAI,CAAC,wBAAwB,CAAC,GAAG,CAAC,UAAU,CAAC,EAAE,CAAC;QAC9C,MAAM,cAAc,CAAC,IAAI,KAAK,CAAC,8FAA8F,CAAC,CAAC,CAAC;IAClI,CAAC;IAED,+FAA+F;IAC/F,oEAAoE;IACpE,MAAM,KAAK,GAAG,qBAAqB,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;IAChD,IAAI,SAAS,GAAG,EAAE,CAAC;IACnB,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;QACzB,MAAM,GAAG,GAAG,MAAM,0BAA0B,CAAC,EAAE,UAAU,EAAE,GAAG,CAAC,UAAU,EAAE,cAAc,EAAE,GAAG,CAAC,cAAc,EAAE,IAAI,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE,IAAI,EAAE,EAAE,CAAC,CAAC;QACxJ,IAAI,SAAS,CAAC,MAAM,KAAK,CAAC;YAAE,SAAS,GAAG,GAAG,CAAC,EAAE,CAAC;IACjD,CAAC;IACD,OAAO,EAAE,SAAS,EAAE,GAAG,CAAC,cAAc,EAAE,SAAS,EAAE,SAAS,IAAI,SAAS,EAAE,CAAC;AAC9E,CAAC;AAED,MAAM,CAAC,MAAM,YAAY,GAAY;IACnC,QAAQ,EAAE,OAAO;IACjB,aAAa,EAAE,CAAC,GAAqB,EAAsB,EAAE;QAC3D,iGAAiG;QACjG,wEAAwE;QACxE,MAAM,UAAU,GAAG,GAAG,CAAC,GAAG,CAAC,YAAY,CAAC,CAAC;QACzC,MAAM,cAAc,GAAG,GAAG,CAAC,GAAG,CAAC,gBAAgB,CAAC,CAAC;QACjD,OAAO,UAAU,IAAI,cAAc,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,OAAO,EAAE,UAAU,EAAE,cAAc,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;IACjG,CAAC;IACD,aAAa,EAAE,CAAC,MAAM,EAAE,IAAI,EAAE,EAAE,CAAC,kBAAkB,CAAC,MAAqB,EAAE,IAAI,CAAC;IAChF,eAAe,EAAE,CAAC,MAAM,EAAE,IAAI,EAAE,IAAsB,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,SAAS,IAAI,aAAa,CAAC,CAAC,MAAqB,EAAE,IAAI,CAAC;IACzH,qBAAqB,EAAE,CAAC,MAAM,EAAE,EAAE,CAAC,sBAAuB,MAAsB,CAAC,cAAc,EAAE;IACjG,kBAAkB,EAAE,CAAC,MAAM,EAAE,EAAE,CAAE,MAAsB,CAAC,cAAc;IACtE,WAAW,EAAE,gBAAgB;IAC7B,oBAAoB,EAAE,yBAAyB;CAChD,CAAC"}

package/dist/agent/channels/teams-reaction-feedback.d.ts

@@ -0,0 +1,22 @@
+import { type ReactionIngestOutcome, type ReactionSinkDeps } from "@open-everywhere/core/agent/adapter-api.js";
+import type { TeamsReactionActivity } from "./teams-stop.js";
+/** Injected seams, so parse + guard + record is unit-tested against stubs with no Bot registration. */
+export interface TeamsReactionFeedbackDeps {
+    readonly sink: ReactionSinkDeps;
+}
+/** Production deps: the live audit/telemetry sink core already owns. There is no Teams-specific
+ *  sink — the whole point of the seam is that the durable row is written in ONE place. */
+export declare function liveTeamsReactionFeedbackDeps(): TeamsReactionFeedbackDeps;
+/**
+ * Ingest every reaction one Teams `messageReaction` activity carries. Returns one outcome per
+ * reaction — added first, then removed — so a caller's log says what happened to each.
+ *
+ * It NEVER THROWS into the caller: core's sinks are best-effort by contract, and a lost feedback row
+ * must never cost the ingress its ack.
+ *
+ * An activity with nothing to ingest returns an EMPTY array. That is the honest answer for a bot's
+ * own reaction, an activity with no reactor, and an activity naming no conversation — none of the
+ * three is a reaction from a person on a message this deployment can key.
+ */
+export declare function routeTeamsReactionFeedback(rx: TeamsReactionActivity, deps: TeamsReactionFeedbackDeps): Promise<readonly ReactionIngestOutcome[]>;
+//# sourceMappingURL=teams-reaction-feedback.d.ts.map

package/dist/agent/channels/teams-reaction-feedback.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-reaction-feedback.d.ts","sourceRoot":"","sources":["../../../agent/channels/teams-reaction-feedback.ts"],"names":[],"mappings":"AAmCA,OAAO,EAKL,KAAK,qBAAqB,EAC1B,KAAK,gBAAgB,EACtB,MAAM,4CAA4C,CAAC;AAEpD,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,iBAAiB,CAAC;AAE7D,uGAAuG;AACvG,MAAM,WAAW,yBAAyB;IACxC,QAAQ,CAAC,IAAI,EAAE,gBAAgB,CAAC;CACjC;AAED;0FAC0F;AAC1F,wBAAgB,6BAA6B,IAAI,yBAAyB,CAEzE;AAQD;;;;;;;;;;GAUG;AACH,wBAAsB,0BAA0B,CAC9C,EAAE,EAAE,qBAAqB,EACzB,IAAI,EAAE,yBAAyB,GAC9B,OAAO,CAAC,SAAS,qBAAqB,EAAE,CAAC,CAiD3C"}