@memberjunction/ai-bridge-teams 0.0.1 → 5.42.0

package/README.md

@@ -1,45 +1,111 @@
 # @memberjunction/ai-bridge-teams
 
-## ⚠️ IMPORTANT NOTICE ⚠️
-
-**This package is created solely for the purpose of setting up OIDC (OpenID Connect) trusted publishing with npm.**
-
-This is **NOT** a functional package and contains **NO** code or functionality beyond the OIDC setup configuration.
-
-## Purpose
-
-This package exists to:
-1. Configure OIDC trusted publishing for the package name `@memberjunction/ai-bridge-teams`
-2. Enable secure, token-less publishing from CI/CD workflows
-3. Establish provenance for packages published under this name
-
-## What is OIDC Trusted Publishing?
-
-OIDC trusted publishing allows package maintainers to publish packages directly from their CI/CD workflows without needing to manage npm access tokens. Instead, it uses OpenID Connect to establish trust between the CI/CD provider (like GitHub Actions) and npm.
-
-## Setup Instructions
-
-To properly configure OIDC trusted publishing for this package:
-
-1. Go to [npmjs.com](https://www.npmjs.com/) and navigate to your package settings
-2. Configure the trusted publisher (e.g., GitHub Actions)
-3. Specify the repository and workflow that should be allowed to publish
-4. Use the configured workflow to publish your actual package
-
-## DO NOT USE THIS PACKAGE
-
-This package is a placeholder for OIDC configuration only. It:
-- Contains no executable code
-- Provides no functionality
-- Should not be installed as a dependency
-- Exists only for administrative purposes
-
-## More Information
-
-For more details about npm's trusted publishing feature, see:
-- [npm Trusted Publishing Documentation](https://docs.npmjs.com/generating-provenance-statements)
-- [GitHub Actions OIDC Documentation](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)
-
----
-
-**Maintained for OIDC setup purposes only**
+The **Microsoft Teams** Realtime Bridge driver in MemberJunction's Realtime Bridges program. It connects
+the one realtime agent engine to a **Teams meeting**: bidirectional audio, a diarized participant roster,
+participant mute, Teams meeting chat, and a **Meeting Controls** facilitator channel — all behind an
+injectable Teams calling-bot SDK seam so the driver builds and unit-tests with **no network and no real
+Teams / Azure Communication Services SDK**. It is a structural mirror of the reference
+[`@memberjunction/ai-bridge-zoom`](../BridgeZoom/README.md) driver.
+
+See the [Realtime Bridges Guide](../../../../guides/REALTIME_BRIDGES_GUIDE.md) and
+[`/plans/realtime/realtime-bridges-architecture.md`](../../../../plans/realtime/realtime-bridges-architecture.md)
+(§3 provider abstraction, §4b channels, §8 Microsoft Teams capability row) for the full architecture.
+
+## Install
+
+```bash
+npm install @memberjunction/ai-bridge-teams
+```
+
+## What it provides
+
+- **`TeamsBridge`** — `@RegisterClass(BaseRealtimeBridge, 'TeamsBridge')`. The `MJ: AI Bridge Providers`
+  row with `DriverClass = 'TeamsBridge'` resolves to this driver via the `ClassFactory`. Implements the
+  four `BaseRealtimeBridge` abstracts (`Connect` / `Disconnect` / `SendMedia` / `OnMedia`) and the
+  capability-gated virtuals Teams supports (`GetParticipants`, `OnParticipantChange`), plus
+  `GetMeetingControlsEventSource` for the facilitator channel and a `PostChatMessage` helper.
+- **`ITeamsMeetingSdk`** — the **injectable seam** the driver depends on instead of the real SDK.
+- **`TeamsMeetingControlsEventSource`** — adapts the seam's roster / hand-raise / speaking / mute into
+  the bridge's `IBridgeMeetingControlsEventSource`, so the engine wires the Meeting Controls channel.
+
+## Capability coverage (the Microsoft Teams seed row)
+
+| Capability | Status |
+|---|---|
+| On-demand + scheduled + invite + **native invite** join | ✅ |
+| Inbound routing | ✅ |
+| Audio in / out | ✅ |
+| Video in/out, Screen in/out (directional flags) | ✅ (transport carries them; models light audio first) |
+| Speaker diarization (roster + per-speaker labels) | ✅ |
+| Participant mute (Meeting Controls) | ✅ |
+| Teams meeting chat | ✅ |
+| Native raised-hand | ⚠️ Partial — wired where the calling-bot API surfaces it; tolerant of it never firing |
+| DTMF / call transfer / recording | ➖ not Teams-meeting features here — the gated base methods throw `BridgeCapabilityNotSupportedError` |
+
+Capability gating is two-layer (defense-in-depth): the engine checks the provider's `SupportedFeatures`
+first, and the driver re-asserts each flag with `RequireFeature` at the top of its overrides.
+
+### Teams vs. Zoom capability differences
+
+Teams advertises everything Zoom does, **plus** `InviteJoin`, `NativeInvite`, and `InboundRouting` (the
+calendar-invite / marketplace-native-invite / inbound-routing UX), and its native raised-hand is **partial**
+rather than fully reliable. Everything else (audio in/out, directional video/screen, diarized roster,
+mute, meeting chat) maps one-to-one onto the Zoom reference driver.
+
+## The Teams calling-bot SDK seam (`ITeamsMeetingSdk`)
+
+The driver never imports the real Teams / ACS SDK. It depends only on this minimal interface, named after
+Microsoft Teams / Azure Communication Services calling-bot concepts:
+
+```typescript
+export interface ITeamsMeetingSdk {
+    join(args: TeamsJoinArgs): Promise<TeamsJoinResult>;
+    leave(): Promise<void>;
+    sendAudioFrame(pcm: ArrayBuffer): void;                                 // agent's voice out (outbound audio socket)
+    onAudioFrame(cb: (frame: TeamsAudioFrame) => void): void;               // raw per-participant audio in (diarization)
+    onParticipantJoin(cb: (p: TeamsParticipant) => void): void;
+    onParticipantLeave(cb: (id: string) => void): void;
+    onHandRaise(cb: (id: string, raised: boolean) => void): void;           // ⚠️ partial on Teams
+    getParticipants(): Promise<TeamsParticipant[]>;
+    postChatMessage(text: string): Promise<void>;                           // Teams meeting chat thread
+    muteParticipant(participantId: string): Promise<void>;
+    onMeetingEnded(cb: () => void): void;
+}
+```
+
+### Production binding (deployment TODO)
+
+In production this is bound to the **Azure Communication Services (ACS) calling-bot** SDK plus the
+**Microsoft Graph cloud-communications API** (`/communications/calls`, application-hosted media) for
+per-participant PCM audio, roster events, mute, and Teams meeting-chat posting. Supply a factory via the
+creation seam:
+
+```typescript
+import { TeamsBridge } from '@memberjunction/ai-bridge-teams';
+
+// Once, where bridge drivers are configured:
+//   bridge.SetSdkFactory((config) => new RealTeamsSdkAdapter(config));
+// The adapter implements ITeamsMeetingSdk over the real ACS/Graph SDK. The driver + its tests do not change.
+```
+
+Out of the box, `TeamsBridge` ships **without** the real SDK adapter — `Connect` throws an explicit
+"bind the real Microsoft Teams SDK" error until `SetSdkFactory` is called. Tests inject a `FakeTeamsSdk`.
+
+## Usage (engine-driven)
+
+The bridge is not used directly — `AIBridgeEngine.StartBridgeSession` (`@memberjunction/ai-bridge-server`)
+resolves it from the provider's `DriverClass`, wires the transport seam to the injected
+`IRealtimeSession`, and (when a channel host is supplied) wires the Meeting Controls channel from
+`GetMeetingControlsEventSource`. See the bridge-server package and the guide's "Channel plane" section.
+
+## Testing
+
+`FakeTeamsSdk` (in `src/__tests__/`) is an in-memory `ITeamsMeetingSdk` with drive helpers and capture
+sinks. The suite covers connect/disconnect (incl. parsing the meeting thread id out of the join URL),
+audio in→`OnMedia` (speaker labels) and out→seam, participant join/leave → roster + event source, native
+hand-raise → Meeting Controls perception, capability gating (a feature Teams lacks throws), and chat — all
+with no network.
+
+```bash
+cd packages/AI/Providers/BridgeTeams && npm run test
+```

package/dist/index.d.ts

@@ -0,0 +1,6 @@
+export * from './teams-sdk.js';
+export * from './teams-meeting-controls.js';
+export * from './teams-bridge.js';
+export * from './teams-native-sdk.js';
+export * from './register-native.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAC;AAC5B,cAAc,0BAA0B,CAAC;AACzC,cAAc,gBAAgB,CAAC;AAC/B,cAAc,oBAAoB,CAAC;AACnC,cAAc,mBAAmB,CAAC"}

package/dist/index.js

@@ -0,0 +1,13 @@
+export * from './teams-sdk.js';
+export * from './teams-meeting-controls.js';
+export * from './teams-bridge.js';
+export * from './teams-native-sdk.js';
+export * from './register-native.js';
+import { LoadTeamsBridge } from './teams-bridge.js';
+import { RegisterTeamsNativeSdk } from './register-native.js';
+// Static reference so bundlers cannot tree-shake the @RegisterClass(BaseRealtimeBridge, 'TeamsBridge')
+// registration. Calling the no-op here keeps the driver resolvable by the engine's ClassFactory.
+LoadTeamsBridge();
+// Register Teams's native two-way SDK binding so the engine auto-binds it at StartBridgeSession.
+RegisterTeamsNativeSdk();
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAC;AAC5B,cAAc,0BAA0B,CAAC;AACzC,cAAc,gBAAgB,CAAC;AAC/B,cAAc,oBAAoB,CAAC;AACnC,cAAc,mBAAmB,CAAC;AAElC,OAAO,EAAE,eAAe,EAAE,MAAM,gBAAgB,CAAC;AACjD,OAAO,EAAE,sBAAsB,EAAE,MAAM,mBAAmB,CAAC;AAE3D,uGAAuG;AACvG,iGAAiG;AACjG,eAAe,EAAE,CAAC;AAClB,iGAAiG;AACjG,sBAAsB,EAAE,CAAC"}

package/dist/register-native.d.ts

@@ -0,0 +1,19 @@
+/**
+ * @fileoverview Registers the Teams **native two-way** SDK binding into the {@link BridgeNativeSdkRegistry}
+ * so `AIBridgeEngine.StartBridgeSession` auto-binds it onto a resolved `TeamsBridge` before connect — no
+ * per-deployment wiring needed. The typed downcast + `SetSdkFactory` stay confined here (where the concrete
+ * `TeamsBridge` type is known), keeping the engine seam free of provider types.
+ *
+ * A host can still override per-session via `StartBridgeSessionParams.BindSdk` — e.g. to use a different
+ * Teams binding instead of the native two-way default.
+ *
+ * @module @memberjunction/ai-bridge-teams
+ * @author MemberJunction.com
+ */
+/**
+ * Registers Teams's native two-way binding. Idempotent (latest-wins in the registry), and invoked from the
+ * package `index.ts` so merely importing `@memberjunction/ai-bridge-teams` wires the default binding. Also
+ * exported as a tree-shake-safe no-op-returning function callers can reference to force-retain the module.
+ */
+export declare function RegisterTeamsNativeSdk(): void;
+//# sourceMappingURL=register-native.d.ts.map

package/dist/register-native.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"register-native.d.ts","sourceRoot":"","sources":["../src/register-native.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AASH;;;;GAIG;AACH,wBAAgB,sBAAsB,IAAI,IAAI,CAO7C"}

package/dist/register-native.js

@@ -0,0 +1,32 @@
+/**
+ * @fileoverview Registers the Teams **native two-way** SDK binding into the {@link BridgeNativeSdkRegistry}
+ * so `AIBridgeEngine.StartBridgeSession` auto-binds it onto a resolved `TeamsBridge` before connect — no
+ * per-deployment wiring needed. The typed downcast + `SetSdkFactory` stay confined here (where the concrete
+ * `TeamsBridge` type is known), keeping the engine seam free of provider types.
+ *
+ * A host can still override per-session via `StartBridgeSessionParams.BindSdk` — e.g. to use a different
+ * Teams binding instead of the native two-way default.
+ *
+ * @module @memberjunction/ai-bridge-teams
+ * @author MemberJunction.com
+ */
+import { BridgeNativeSdkRegistry } from '@memberjunction/ai-bridge-base';
+import { BindTeamsNative } from './teams-native-sdk.js';
+/** The `MJ: AI Bridge Providers.DriverClass` value the Teams provider row carries. */
+const TEAMS_DRIVER_CLASS = 'TeamsBridge';
+/**
+ * Registers Teams's native two-way binding. Idempotent (latest-wins in the registry), and invoked from the
+ * package `index.ts` so merely importing `@memberjunction/ai-bridge-teams` wires the default binding. Also
+ * exported as a tree-shake-safe no-op-returning function callers can reference to force-retain the module.
+ */
+export function RegisterTeamsNativeSdk() {
+    BridgeNativeSdkRegistry.Instance.Register(TEAMS_DRIVER_CLASS, (driver) => {
+        // Safe downcast: the registry is keyed by DriverClass, so the engine only ever applies this to the
+        // TeamsBridge it resolved for 'TeamsBridge'. BindTeamsNative() defaults to the lazy native loader,
+        // which reads NativeModuleSpecifier from the per-session Configuration.
+        driver.SetSdkFactory(BindTeamsNative());
+    });
+}
+// Register on import (mirrors the LoadTeamsBridge() tree-shake pattern in index.ts).
+RegisterTeamsNativeSdk();
+//# sourceMappingURL=register-native.js.map

package/dist/register-native.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"register-native.js","sourceRoot":"","sources":["../src/register-native.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,uBAAuB,EAAsB,MAAM,gCAAgC,CAAC;AAE7F,OAAO,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAErD,sFAAsF;AACtF,MAAM,kBAAkB,GAAG,aAAa,CAAC;AAEzC;;;;GAIG;AACH,MAAM,UAAU,sBAAsB;IAClC,uBAAuB,CAAC,QAAQ,CAAC,QAAQ,CAAC,kBAAkB,EAAE,CAAC,MAA0B,EAAE,EAAE;QACzF,mGAAmG;QACnG,mGAAmG;QACnG,wEAAwE;QACvE,MAAsB,CAAC,aAAa,CAAC,eAAe,EAAE,CAAC,CAAC;IAC7D,CAAC,CAAC,CAAC;AACP,CAAC;AAED,qFAAqF;AACrF,sBAAsB,EAAE,CAAC"}

package/dist/teams-bridge.d.ts

@@ -0,0 +1,155 @@
+/**
+ * @fileoverview `TeamsBridge` — the **Microsoft Teams** platform Realtime Bridge driver, connecting the
+ * one realtime agent engine to a **Teams meeting**. Implements the {@link BaseRealtimeBridge} contract
+ * against an injectable {@link ITeamsMeetingSdk} seam so it builds + unit-tests with NO network and NO
+ * real Teams / Azure Communication Services SDK (the Gemini `connectLiveSession` testability pattern).
+ * Structurally mirrors `ZoomBridge` (the reference driver) — only the platform names + join-coordinate
+ * parsing differ.
+ *
+ * Teams capability coverage (per the §8 seed row): on-demand + scheduled + invite + native-invite join,
+ * inbound routing, audio in/out (video/screen directional flags carried by transport), a diarized roster
+ * (`SpeakerDiarization`), participant mute + Teams meeting chat (via the Meeting Controls channel). Native
+ * raised-hand is ⚠️ partial over the calling-bot API — wired where the platform surfaces it, tolerant of
+ * it never firing. Telephony features (DTMF / transfer / recording) are NOT Teams-meeting features here,
+ * so those virtual base methods keep throwing `BridgeCapabilityNotSupportedError`.
+ *
+ * @module @memberjunction/ai-bridge-teams
+ * @author MemberJunction.com
+ */
+import { BaseRealtimeBridge, BridgeConnectResult, BridgeDisconnectReason, BridgeMediaFrame, BridgeMediaTrackKind, BridgeParticipantInfo, RealtimeBridgeContext, IBridgeMeetingControlsEventSource } from '@memberjunction/ai-bridge-base';
+import { TeamsMeetingSdkFactory } from './teams-sdk.js';
+/**
+ * The `DriverClass` key {@link TeamsBridge} registers under. A `MJ: AI Bridge Providers` row with
+ * `DriverClass = 'TeamsBridge'` resolves to this driver via the `ClassFactory`.
+ */
+export declare const TEAMS_BRIDGE_DRIVER_CLASS = "TeamsBridge";
+/**
+ * Realtime Bridge driver for **Microsoft Teams meetings**.
+ *
+ * Construct the driver with the default constructor (the engine's `ClassFactory` path) — it lazily
+ * builds the Teams SDK from the {@link sdkFactory} at {@link Connect} time. Tests inject a `FakeTeamsSdk`
+ * by overriding the factory via {@link SetSdkFactory} (the creation seam) before connecting.
+ *
+ * Registered via `@RegisterClass(BaseRealtimeBridge, 'TeamsBridge')`.
+ */
+export declare class TeamsBridge extends BaseRealtimeBridge {
+    /** The live Teams SDK seam for this session, created at {@link Connect}. */
+    private sdk;
+    /** The bot's own participant id in the joined meeting (set at {@link Connect}). */
+    private botParticipantId;
+    /** The inbound-media handler registered via {@link OnMedia}; raw audio frames are forwarded to it. */
+    private mediaHandler?;
+    /** The roster-change handler registered via {@link OnParticipantChange}. */
+    private participantHandler?;
+    /** The Meeting Controls event source for this session (only when diarization is supported). */
+    private meetingControls;
+    /**
+     * The SDK creation seam. Defaults to a factory that throws an explicit "bind the real Teams SDK"
+     * error, since this package ships WITHOUT the real SDK adapter (a deployment concern). Production
+     * sets a real factory via {@link SetSdkFactory}; tests inject a `FakeTeamsSdk`.
+     */
+    private sdkFactory;
+    /**
+     * Sets the {@link TeamsMeetingSdkFactory} this driver uses to construct its SDK seam at connect —
+     * the creation seam (mirroring Gemini's overridable `connectLiveSession`). Production binds the
+     * real Teams ACS calling-bot adapter here; tests inject a `FakeTeamsSdk`.
+     *
+     * @param factory The factory that builds the {@link ITeamsMeetingSdk} for a session.
+     */
+    SetSdkFactory(factory: TeamsMeetingSdkFactory): void;
+    /**
+     * Joins the Teams meeting and brings the bot online. Captures the capability context, builds the SDK
+     * from the {@link sdkFactory}, wires the inbound raw-audio path and meeting-ended callback, joins,
+     * and (when the provider diarizes) constructs + seeds the Meeting Controls event source.
+     *
+     * @param ctx The bridge context (features, provider name, the join URL as `Address`, config).
+     * @returns The bot participant + call (external connection) identifiers, persisted by the engine.
+     */
+    Connect(ctx: RealtimeBridgeContext): Promise<BridgeConnectResult>;
+    /**
+     * Leaves the Teams meeting and releases all SDK resources. Tolerant of teardown errors.
+     *
+     * @param _reason Why the disconnect happened (Teams teardown is uniform; the bot simply leaves).
+     */
+    Disconnect(_reason: BridgeDisconnectReason): Promise<void>;
+    /**
+     * Sends an outbound media frame into the meeting. Audio is fed to the SDK's outbound audio-socket
+     * path; video/screen frames are gated by the directional capability flags (the transport carries
+     * them, and the SDK send is a deployment-time binding TODO — today the models emit audio).
+     *
+     * @param track The outbound track the frame targets.
+     * @param frame The media frame to send.
+     */
+    SendMedia(track: BridgeMediaTrackKind, frame: BridgeMediaFrame): void;
+    /**
+     * Registers the inbound-media handler. The driver forwards each raw per-participant audio frame
+     * (with its speaker label) to this handler; the engine routes it to `IRealtimeSession.SendInput`.
+     *
+     * @param handler Invoked with each inbound media frame.
+     */
+    OnMedia(handler: (frame: BridgeMediaFrame) => void): void;
+    /**
+     * Returns the current Teams participant roster (gated by `SpeakerDiarization`). Re-asserts the flag
+     * (defense-in-depth) so even an engine-bypassing caller cannot pull a roster a disabled provider
+     * forbids.
+     *
+     * @returns The current participants.
+     * @throws {BridgeCapabilityNotSupportedError} when diarization is not enabled for the provider.
+     */
+    GetParticipants(): Promise<BridgeParticipantInfo[]>;
+    /**
+     * Registers a roster-change handler (gated by `SpeakerDiarization`). The driver fires it from the
+     * SDK's participant join/leave stream with the full current roster.
+     *
+     * @param handler Invoked with the updated participant list on each change.
+     * @throws {BridgeCapabilityNotSupportedError} when diarization is not enabled.
+     */
+    OnParticipantChange(handler: (participants: BridgeParticipantInfo[]) => void): void;
+    /**
+     * Returns the Teams Meeting Controls event source for this session (roster · hand-raise · speaking ·
+     * mute), or `null` when diarization is off (no roster to facilitate). The engine wires the Meeting
+     * Controls channel from this.
+     */
+    GetMeetingControlsEventSource(): IBridgeMeetingControlsEventSource | null;
+    /**
+     * Posts a message to the Teams meeting chat. Exposed for the channel plane / turn-taking hybrid
+     * mode (the social-cost-free "raise hand"). Best-effort — a chat failure is logged, never fatal.
+     *
+     * @param text The chat message to post.
+     */
+    PostChatMessage(text: string): Promise<void>;
+    /** The bot's participant id in the joined meeting (or `null` before {@link Connect}). */
+    get BotParticipantId(): string | null;
+    /** Wires the SDK's inbound raw-audio callback to a diarized inbound {@link BridgeMediaFrame}. */
+    private wireInboundAudio;
+    /**
+     * Wires the SDK's participant join/leave + hand-raise streams ONCE (the driver is the single owner;
+     * the SDK seam is latest-handler-wins). Each roster change fans out to both the driver's own
+     * roster-change handler and the Meeting Controls source; hand-raise signals (⚠️ partial on Teams)
+     * feed the source.
+     */
+    private wireRoster;
+    /** Pulls the current roster from the SDK and fans it out to both the participant handler + Meeting Controls. */
+    private refreshRoster;
+    /** Handles the SDK's meeting-ended signal: surface an empty roster so the engine sees everyone gone. */
+    private handleMeetingEnded;
+    /** Builds the SDK join args from the bridge context (Address is the meeting join URL). */
+    private buildJoinArgs;
+    /**
+     * Extracts the meeting thread id from a Teams `meetup-join` URL when present, else `undefined`. The
+     * thread id is the `19:meeting_...@thread.v2` segment embedded (URL-encoded) in the join link.
+     * Tolerant — a non-matching address yields `undefined` so the SDK can resolve coordinates itself.
+     */
+    private parseThreadId;
+    /** Returns the PCM bytes of an outbound audio frame, preferring the binary payload. */
+    private framePcm;
+    /** Decodes a base64 payload to an `ArrayBuffer` (Node `Buffer` fast path, `atob` fallback). */
+    private decodeBase64;
+}
+/**
+ * Tree-shaking-prevention loader. Modern bundlers cannot see the `@RegisterClass` dynamic registration
+ * of {@link TeamsBridge} and may eliminate it. Import and call this no-op from a static code path
+ * (the package entry point does) so the `ClassFactory` can resolve `'TeamsBridge'`.
+ */
+export declare function LoadTeamsBridge(): void;
+//# sourceMappingURL=teams-bridge.d.ts.map

package/dist/teams-bridge.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"teams-bridge.d.ts","sourceRoot":"","sources":["../src/teams-bridge.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAIH,OAAO,EACH,kBAAkB,EAClB,mBAAmB,EACnB,sBAAsB,EACtB,gBAAgB,EAChB,oBAAoB,EACpB,qBAAqB,EAErB,qBAAqB,EACrB,iCAAiC,EACpC,MAAM,gCAAgC,CAAC;AACxC,OAAO,EAEH,sBAAsB,EAKzB,MAAM,aAAa,CAAC;AAGrB;;;GAGG;AACH,eAAO,MAAM,yBAAyB,gBAAgB,CAAC;AA8BvD;;;;;;;;GAQG;AACH,qBACa,WAAY,SAAQ,kBAAkB;IAC/C,4EAA4E;IAC5E,OAAO,CAAC,GAAG,CAAiC;IAE5C,mFAAmF;IACnF,OAAO,CAAC,gBAAgB,CAAuB;IAE/C,sGAAsG;IACtG,OAAO,CAAC,YAAY,CAAC,CAAoC;IAEzD,4EAA4E;IAC5E,OAAO,CAAC,kBAAkB,CAAC,CAAkD;IAE7E,+FAA+F;IAC/F,OAAO,CAAC,eAAe,CAAgD;IAEvE;;;;OAIG;IACH,OAAO,CAAC,UAAU,CAMhB;IAEF;;;;;;OAMG;IACI,aAAa,CAAC,OAAO,EAAE,sBAAsB,GAAG,IAAI;IAM3D;;;;;;;OAOG;IACU,OAAO,CAAC,GAAG,EAAE,qBAAqB,GAAG,OAAO,CAAC,mBAAmB,CAAC;IA2B9E;;;;OAIG;IACU,UAAU,CAAC,OAAO,EAAE,sBAAsB,GAAG,OAAO,CAAC,IAAI,CAAC;IAgBvE;;;;;;;OAOG;IACI,SAAS,CAAC,KAAK,EAAE,oBAAoB,EAAE,KAAK,EAAE,gBAAgB,GAAG,IAAI;IAuB5E;;;;;OAKG;IACI,OAAO,CAAC,OAAO,EAAE,CAAC,KAAK,EAAE,gBAAgB,KAAK,IAAI,GAAG,IAAI;IAMhE;;;;;;;OAOG;IACmB,eAAe,IAAI,OAAO,CAAC,qBAAqB,EAAE,CAAC;IASzE;;;;;;OAMG;IACa,mBAAmB,CAAC,OAAO,EAAE,CAAC,YAAY,EAAE,qBAAqB,EAAE,KAAK,IAAI,GAAG,IAAI;IAKnG;;;;OAIG;IACa,6BAA6B,IAAI,iCAAiC,GAAG,IAAI;IAMzF;;;;;OAKG;IACU,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC;IAWzD,yFAAyF;IACzF,IAAW,gBAAgB,IAAI,MAAM,GAAG,IAAI,CAE3C;IAID,iGAAiG;IACjG,OAAO,CAAC,gBAAgB;IAWxB;;;;;OAKG;IACH,OAAO,CAAC,UAAU;IAMlB,gHAAgH;YAClG,aAAa;IAU3B,wGAAwG;IACxG,OAAO,CAAC,kBAAkB;IAK1B,0FAA0F;IAC1F,OAAO,CAAC,aAAa;IAWrB;;;;OAIG;IACH,OAAO,CAAC,aAAa;IAerB,uFAAuF;IACvF,OAAO,CAAC,QAAQ;IAUhB,+FAA+F;IAC/F,OAAO,CAAC,YAAY;CAevB;AAED;;;;GAIG;AACH,wBAAgB,eAAe,IAAI,IAAI,CAEtC"}