@convai/web-sdk 1.8.0-beta.5 → 1.8.0-beta.7

package/README.md

@@ -2,7 +2,7 @@
 
 **Real-time conversational AI characters for the web.**
 
-[![npm](https://img.shields.io/badge/npm-1.7.0-blue)](https://www.npmjs.com/package/@convai/web-sdk)
+[![npm](https://img.shields.io/badge/npm-1.8.0--beta.7-blue)](https://www.npmjs.com/package/@convai/web-sdk)
 [![TypeScript](https://img.shields.io/badge/TypeScript-first-3178C6)](https://www.typescriptlang.org/)
 [![License](https://img.shields.io/badge/license-Apache--2.0-green)](./LICENSE)
 
@@ -10,14 +10,28 @@ TypeScript-first SDK for embedding Convai AI characters into React and vanilla J
 
 ---
 
-## What's new in 1.7.0
+## What's new in 1.8.0 (beta)
+
+Install the beta with `npm install @convai/web-sdk@beta`.
+
+- **Multi-character rooms** — connect a roster of characters with the `characters` config option (two copies of one character are two independent members), switch who answers with `setInteractionTarget()`, add or remove members live with `updateCharacterRoster()`, and let other participants join the same room with `joinRoom()`. Every transcript line, audio track and readiness event is attributed to a `membershipId`. [Usage below.](#multi-character-rooms-beta)
+- **Agentic actions and canonical model output (v2)** — opt in with `capabilities`, declare client-executed tools in `actionConfig.tools`, consume typed `modelOutput` envelopes, return results with `sendActionResultAndWait()` for a correlated server acknowledgement, and read the raw provider stream through `botLlmTextRaw`. `visionPromptMode: "disabled"` keeps scene context without advertising visual perception. [Usage below.](#agentic-actions-and-canonical-model-output-v2)
+- **Published text chat** — a credential-free, text-only connection for public chat pages: `connectWithPublicationGrant()`, `connectionType: "text"`, and the self-contained `<convai-chat>` browser bundle. [Usage below.](#published-text-chat)
+- **Typed events** — `client.on(event, callback)` infers each callback's payload from the exported `ConvaiEventMap`, so `botReady`, `modelOutput`, `characterStatus` and the rest are checked at compile time. See the [events reference](docs/convai_events.md).
+- **Local transcript lines and usage updates** — `appendMessage()` inserts a line into the transcript without sending anything, and `toggleUsageUpdates(true)` opts into per-turn `usageUpdate` cost breakdowns.
+- **Character versioning** — connect to a character's editable draft, its promoted latest release, or an immutable tag with the `characterVersion` config option, and list, compare, release, promote, fork and discard versions through `client.characterVersions`. [Usage below.](#character-versioning-beta)
+- **SSE interaction transport** — text-only streamed interactions through the interaction API, selected by `interactionApiUrl`; the one transport that runs under Node. [Usage below.](#sse-interaction-transport-beta)
+- **Embeddable vanilla widget** — the vanilla widget runs inside a shadow root, with a character header and a connecting overlay, so it can be dropped into any page.
+- **Node-importable dist** — `@convai/web-sdk/core`, `/vanilla`, `/vanilla/websocket` and `/lipsync-helpers` load in plain Node, SSR and Next.js server components.
+
+### Previously in 1.7.0
 
 - **Character state of mind** — set a temporary generation mood with the `stateOfMind` config option, and change it mid-session with `updateEmotion()` without triggering a response. [Usage below.](#character-state-of-mind)
 - **Send-ahead enabled by default** — NeuroSync lipsync ahead-delivery is now on by default, reversing the 1.6.0 opt-in. Fall back to the legacy paced path with `blendshapeConfig.deliver_chunks_ahead: false`.
 - **Lipsync naturalness pipeline** — modular naturalness processing with a tuned MetaHuman profile.
 - **Adaptive glass widget styling** — `ConvaiWidget` adapts to light and dark backgrounds.
 
-### Previously in 1.6.0
+### 1.6.0
 
 - **Narrative Design template keys** — personalize one narrative graph per session: seed values at connect with the `narrativeTemplateKeys` config option, replace them mid-session with `updateTemplateKeys()`. [Usage below.](#narrative-design-template-keys)
 - **Typed parameterized actions** — `actionResponse` is now typed via the exported `ConvaiAction` / `ActionResponseEvent`, including the `target` of parameterized actions. [Usage below.](#actions)
@@ -34,6 +48,11 @@ TypeScript-first SDK for embedding Convai AI characters into React and vanilla J
 - **Dynamic context & vision** — inject text state, scene metadata, and LiveKit video frames mid-session
 - **Actions & Narrative Design** — typed action decisions with parameterized targets, named triggers, and per-session template keys
 - **Long-term memory** — persistent cross-session memories scoped to each end user
+- **Multi-character rooms** — a roster of characters in one room, per-member attribution, live roster changes
+- **Agentic actions (v2)** — client-executed tools, canonical model output, acknowledged action results, raw provider stream
+- **Published text chat** — grant-based, credential-free text sessions and a drop-in `<convai-chat>` element
+- **Typed events** — every `client.on` payload typed through `ConvaiEventMap`
+- **Character versioning** — connect to a draft, latest, or tagged version, and manage releases from the client
 - **File upload** — send images to the character during a live session
 - **WebSocket transport** — opt-in alternative to WebRTC for constrained networks
 - **Auth tokens** — server-side token exchange for production deployments
@@ -91,6 +110,114 @@ window.addEventListener("beforeunload", () => {
 });
 ```
 
+### Published text chat
+
+See the [Published text chat guide](./docs/convai_published_chat.md) for
+React and vanilla integrations, lifecycle behavior, and the complete API
+reference.
+
+Published chat pages use a short-lived launch grant instead of the publisher's
+API key. Native Web SDK integration is the recommended embed path; an iframe is
+not required. Obtain the grant from the public Character API and pass it to the
+core client:
+
+```ts
+import { ConvaiClient } from '@convai/web-sdk/core';
+import { requestPublishedChatGrant } from '@convai/web-sdk/embed';
+
+const launchToken = await requestPublishedChatGrant(
+  `${characterApiUrl}/chat-publications/${publicationId}/launch-grants`,
+);
+const client = new ConvaiClient();
+const unsubscribe = client.on('botReady', () => {
+  unsubscribe();
+  client.sendUserTextMessage('Hello!');
+});
+await client.connectWithPublicationGrant(launchToken);
+```
+
+The grant is single-use and is not retained for reconnect. Request a new grant
+for each new session. The SDK attaches a browser-generated logical attempt ID
+and retries one transient grant exchange with that same ID, so a response lost
+after server-side consumption does not strand the token or create a duplicate
+session. An application performing its own retry may pass the same
+`connectAttemptId` option with the same launch token. Published chat is
+text-only; the server-issued room token does not permit publishing microphone
+or camera tracks.
+
+The `@convai/web-sdk/embed` browser element creates its own per-browser
+requester identifier. If a server or SSR integration calls its published-chat
+grant helpers directly, it must pass a caller-scoped requester identifier; do
+not reuse a process-wide identifier across visitors.
+
+When using `ConvaiWidget`, provide `requestPublicationGrant` so Reset,
+Disconnect, and later reopen operations mint a new grant instead of attempting
+to reuse the consumed token:
+
+```tsx
+<ConvaiWidget
+  convaiClient={client}
+  publishedChatDescriptor={{
+    display_name: publication.display_name,
+    image_url: publication.image_url,
+  }}
+  requestPublicationGrant={async () => {
+    const response = await fetch(`/api/chat/${publicationId}/grant`, {
+      method: 'POST',
+    });
+    if (!response.ok) throw new Error('Unable to relaunch published chat');
+    return (await response.json()).launch_token;
+  }}
+/>
+```
+
+For copy/paste installation without an application build step, deploy the
+versioned browser artifact at `dist/embed/chat-embed-v1.js` and use its native
+custom element:
+
+```html
+<script
+  type="module"
+  src="https://cdn.jsdelivr.net/npm/@convai/web-sdk@<SDK_VERSION>/dist/embed/chat-embed-v1.js"
+></script>
+<convai-chat publication-id="PUBLICATION_UUID"></convai-chat>
+```
+
+The element renders directly in the host page with Shadow DOM style isolation,
+automatically mints a fresh grant per connection, and emits `convai-ready`,
+`convai-disconnect`, and `convai-error` DOM events. The production bundle uses
+`https://api.convai.com` and `https://realtime-api.convai.com` only as defaults
+for a hand-written SaaS integration. Platform-generated snippets always emit
+the deployment's public Character API and Core endpoints explicitly, so an
+on-prem or non-production embed never falls through to another deployment and
+still requires no credential:
+
+```html
+<convai-chat
+  publication-id="PUBLICATION_UUID"
+  publication-api-url="https://character-api.example.com"
+  core-url="https://realtime.example.com"
+></convai-chat>
+```
+
+Replace `<SDK_VERSION>` with the exact published package version. Do not use
+`latest`: generated embed snippets must stay bound to the SDK version validated
+for their target environment.
+
+Descriptor and grant endpoints must allow credential-free cross-origin `GET`
+and `POST` requests. The embed never receives a publisher API key, character
+configuration, or reusable launch token.
+
+For customer-managed and GovCloud deployments, the repository also builds a
+browser-only image from `deploy/published-chat/Dockerfile`. It serves the exact
+released bundle at `/sdk/chat-embed-v1.js` on port `8080`, plus `/healthz`, and
+contains no API key or cloud identity. The manual `build-onprem` workflow
+requires an immutable semver tag matching `package.json`, refuses to overwrite
+an existing Docker Hub tag, and publishes both amd64 and arm64 images. Pin the
+resulting digest in the deployment repository; do not make an on-prem browser
+depend on jsDelivr, npm availability, GCP workload identity, or the Experience
+application image.
+
 ---
 
 ## Documentation
@@ -115,6 +242,9 @@ Full documentation is at **<a href="https://docs.convai.com/api-docs/plugins-and
 | <a href="https://docs.convai.com/api-docs/plugins-and-integrations/web-plugins/convai-web-sdk/websocket-transport-layer" target="_blank" rel="noopener noreferrer">WebSocket Transport</a> | Alternative transport for WebRTC-constrained environments                                          |
 | <a href="https://docs.convai.com/api-docs/plugins-and-integrations/web-plugins/convai-web-sdk" target="_blank" rel="noopener noreferrer">SSE Transport</a>                         | Text-only interaction transport; the one that runs under Node                                      |
 | [Character Versioning](docs/convai_character_versioning.md)                                                                                                                              | Connect to a draft, latest, or tagged version; list, compare, release and promote versions         |
+| [Multi-Character Rooms](docs/convai_multi_character.md)                                                                                                                                  | Rosters, `joinRoom`, interaction targets, live roster updates, per-member attribution              |
+| [Published Text Chat](docs/convai_published_chat.md)                                                                                                                                     | Grant-based text-only sessions, `<convai-chat>`, lifecycle and API reference                       |
+| [Events Reference (local)](docs/convai_events.md)                                                                                                                                        | Every event with its typed payload, including the v2 and multi-character events                    |
 
 ---
 
@@ -126,6 +256,8 @@ Full documentation is at **<a href="https://docs.convai.com/api-docs/plugins-and
 | `@convai/web-sdk/react`             | Same as default (React-explicit alias)                                                                          |
 | `@convai/web-sdk/vanilla`           | `ConvaiClient`, `createConvaiWidget`, `AudioRenderer`                                                           |
 | `@convai/web-sdk/core`              | Framework-agnostic `ConvaiClient`, managers, and all types                                                      |
+| `@convai/web-sdk/embed`             | Server-safe publication descriptor and grant helpers                                                            |
+| `@convai/web-sdk/embed/browser`     | Self-contained browser bundle that registers `<convai-chat>`                                                    |
 | `@convai/web-sdk/lipsync-helpers`   | Blendshape format utilities and queue helpers                                                                   |
 | `@convai/web-sdk/vanilla/websocket` | **Opt-in.** Registers the WebSocket transport. Import alongside `/vanilla` when using `transport: "websocket"`. |
 
@@ -184,28 +316,103 @@ Full guide: [SSE Interaction Transport](docs/convai_sse_transport.md).
 
 ## Character versioning (beta)
 
-Connect to a character's editable draft, its promoted latest release, or an immutable tag, and
-manage those versions from the same client:
+Every character has an editable **draft** and, once released, immutable **tagged versions**
+(`1.0`, `1.1`, …). A movable `latest` pointer names the release the runtime uses when a client
+connects without a selector. Pick the version to run with `characterVersion`:
 
-```ts
-const client = new ConvaiClient({
+| `characterVersion` | Runs |
+| ------------------ | ----------------------------------------------------------------- |
+| *(omitted)*        | The effective latest — how characters that predate versioning behave |
+| `"draft"`          | The editable draft, for testing unreleased changes                |
+| `"latest"`         | The promoted latest release, explicitly                           |
+| `"1.2"` / `"1.2.3"` | An immutable tagged version                                      |
+
+```tsx
+const client = useConvaiClient({
   apiKey: "...",
   characterId: "...",
-  characterVersion: "draft", // or "latest", "1.2" — omit for the effective latest
+  characterVersion: "draft",
 });
+```
+
+On the wire the selector is joined to the id as `<uuid>-draft`; `client.characterId` keeps
+returning the bare UUID, and `client.characterReference` returns the joined form.
+
+Manage versions from the same client — `client.characterVersions` is available as soon as the
+config has an `apiKey`, before connecting:
 
+```ts
 const versions = client.characterVersions!;
-const { has_unpublished_changes } = await versions.list();
-if (has_unpublished_changes) await versions.create("1.1", { makeLatest: true });
-await client.connect();
+
+const { has_unpublished_changes, draft_revision_id } = await versions.list();
+const diff = await versions.diff("latest", "draft", { view: "semantic" });
+
+await versions.create("1.1", { makeLatest: true }); // release the draft as a tag
+await versions.promote("1.0");                      // roll back: latest → 1.0
+await versions.discardDraft(draft_revision_id!);    // throw away unreleased edits
 ```
 
-Explicit selectors are resolved by the runtime through the Character REST platform; staging has
-this today and production returns `503` for explicit selectors until it is promoted there.
+`CharacterVersionManager` can also be constructed standalone with an `apiKey` or a Convai
+personal access token; every method rejects with `CharacterApiError` (`status`, `detail`) on a
+non-2xx answer. Point `characterApiUrl` at `https://api2-stg.convai.com` to author against
+staging.
+
+Explicit selectors are resolved by the runtime through the Character REST platform. Staging has
+this today; production answers explicit selectors with `503` until it is promoted there.
 Full guide: [Character Versioning](docs/convai_character_versioning.md).
 
 ---
 
+
+## Multi-character rooms (beta)
+
+Pass `characters` instead of `characterId` to open a room with several members.
+`characters[0]` answers first; the same character id may appear more than once
+and each entry is an independent member with its own `membershipId`. Roster
+rooms need the LiveKit transport and a nonblank `endUserId`.
+
+```ts
+const client = new ConvaiClient({
+  apiKey: "YOUR_API_KEY",
+  endUserId: "player-42",
+  characters: [
+    { characterId: GUIDE },     // initial active member
+    { characterId: ASSESSOR },
+    { characterId: GUIDE },     // a second, independent copy of the guide
+  ],
+  maxNumParticipants: 2,
+});
+
+client.on("characterReady", (member) => console.log("ready", member.membershipId));
+client.on("characterStatus", ({ membershipId, status, failureCode }) => {
+  if (status === "failed") console.warn(membershipId, failureCode);
+});
+
+await client.connect();
+
+// Route the next user turns to another member; null closes every gate.
+await client.setInteractionTarget(client.characters[1].membershipId);
+
+// Change the roster on a live room.
+await client.updateCharacterRoster({ add: [{ characterId: GUIDE }] });
+await client.updateCharacterRoster({ remove: [client.characters[0].membershipId] });
+
+// Another participant joins the same room without sending any topology.
+await other.joinRoom({ roomSessionId: client.roomSession!.roomSessionId, endUserId: "player-7" });
+```
+
+Key points:
+
+- `characters` and `characterId` are mutually exclusive, and roster entries take a bare character UUID (no `-draft` / `-1.2` selectors).
+- `provisioningStatus` describes dispatch only; a member is usable when its own `characterReady` arrives.
+- Transcript rows, `characterAudioTrack` events and `botReady` payloads carry `membershipId`, so two copies of one character never merge.
+- Room-topology failures throw `ConvaiRoomError` with `status`, `code`, `requestTraceId` and `isRetryable`; the SDK retries `ROSTER_PROVISIONING_IN_PROGRESS` for you (`rosterProvisioningRetry`).
+- Action protocol v2 and `actionConfig.tools` are single-character only and cannot be combined with a roster.
+
+Full reference: [docs/convai_multi_character.md](docs/convai_multi_character.md).
+
+---
+
 ## Vision dynamic context beta
 
 Vision dynamic context is the default WebRTC/LiveKit vision path when `enableVideo: true`. Camera, screen, canvas, and custom video tracks can feed unified vision context; set `visionInputConfig.enabled: false` only when you need to keep the video channel while opting out.
@@ -273,6 +480,119 @@ client.on("actionResponse", ({ actions }: ActionResponseEvent) => {
 });
 ```
 
+### Agentic actions and canonical model output (v2)
+
+The v2 protocol is an explicit opt-in. Existing connections continue to receive
+the v1 `actionResponse` contract. A v2 client declares tools at connect time,
+dispatches only Core-validated `items`, and returns one correlated terminal
+result for every `tool_call`.
+
+```ts
+import { ConvaiClient, type ActionResult } from "@convai/web-sdk/core";
+
+const client = new ConvaiClient({
+  apiKey: "...",
+  characterId: "...",
+  capabilities: {
+    actionProtocolVersion: 2,
+    modelOutputVersion: 2,
+  },
+  actionConfig: {
+    actions: [],
+    objects: [],
+    characters: [],
+    tools: [
+      {
+        name: "search_documents",
+        description: "Search the user's approved document collection",
+        inputSchema: {
+          type: "object",
+          properties: { query: { type: "string" } },
+          required: ["query"],
+        },
+      },
+    ],
+  },
+});
+
+client.on("modelOutput", async (output) => {
+  for (const item of output.items) {
+    if (item.type === "message") renderAssistantText(item.content);
+    if (item.type !== "tool_call") continue;
+
+    let terminalResult: ActionResult;
+    try {
+      const result = await executeApprovedTool(item.name, item.arguments);
+      terminalResult = {
+        id: item.id,
+        status: "completed",
+        output: result,
+      };
+    } catch (error) {
+      terminalResult = {
+        id: item.id,
+        status: "error",
+        error: { message: String(error) },
+      };
+    }
+
+    try {
+      const ack = await client.sendActionResultAndWait(terminalResult, {
+        timeoutMs: 10_000,
+      });
+      markResultReported(item.id, ack.idempotent);
+    } catch (deliveryError) {
+      markResultDeliveryUncertain(item.id, deliveryError);
+      // If appropriate for your session lifecycle, retry `terminalResult`
+      // unchanged. Never execute the tool again merely because its ACK was lost.
+    }
+  }
+});
+```
+
+### Parallel raw provider output (v2)
+
+Model output v2 may provide a separate diagnostics-only raw stream alongside
+the unchanged `bot-llm-text` chat stream. Each chunk carries Core's stable
+logical-turn correlation id and, on newer Core versions, an invocation id:
+
+```ts
+const client = new ConvaiClient({
+  apiKey: "...",
+  characterId: "...",
+  capabilities: { modelOutputVersion: 2 },
+});
+
+client.on("botLlmTextRaw", ({ text, logical_turn_id, output_id }) => {
+  appendRawDiagnostics(output_id ?? logical_turn_id, text);
+});
+```
+
+The SDK ignores this channel unless Core negotiated `modelOutputVersion: 2`.
+Raw chunks never enter `chatMessages`, bot output, TTS, speech, or response
+lifecycle state. They are retained for diagnostics and must never be executed
+or reparsed. The ordinary `bot-llm-text` text and cadence remain unchanged. On
+v2 connections, `ChatMessage.outputId` matches the raw event's optional
+`output_id` and the final `modelOutput.output_id`; `logicalTurnId`/
+`logical_turn_id` still groups every invocation in the user turn. Older v2 Core
+omits the invocation id, so applications can fall back to one turn-level raw
+aggregate. Never correlate by arrival order. When v2 is selected, the SDK suppresses the legacy `actionResponse` compatibility
+projection so an application cannot execute the same operation twice.
+
+Developer-defined visual output uses data-only `extension` items. Applications
+register a renderer for a specific schema and version; unknown schemas use the
+server-provided text fallback or remain unhandled. The SDK never evaluates code
+from a model output.
+
+```ts
+import { ModelOutputExtensionRegistry } from "@convai/web-sdk/core";
+
+const extensions = new ModelOutputExtensionRegistry<HTMLElement>();
+extensions.register("com.example/status-card", 1, ({ payload }) =>
+  renderStatusCard(payload),
+);
+```
+
 ---
 
 ## Narrative Design template keys

package/dist/core/CharacterRoster.d.ts

@@ -0,0 +1,84 @@
+import type { ActiveCharacterChange, CharacterRosterChange, ConvaiCharacterInstance, ConvaiRoomSession, ServerResponseExtras, UpdateCharacterRosterOptions } from "./types.js";
+export declare class CharacterRoster {
+    private _characters;
+    private _activeMembershipId;
+    private _roomSessionId;
+    private _roomName;
+    private _requestTraceId;
+    private _routeEpoch;
+    private _rosterEpoch;
+    private _partialDispatch;
+    /** Character instances in roster order. Empty in single-character mode. */
+    get characters(): ConvaiCharacterInstance[];
+    /** Membership currently receiving user turns, or null. */
+    get activeMembershipId(): string | null;
+    get roomSessionId(): string | null;
+    get routeEpoch(): number;
+    get rosterEpoch(): number;
+    /** True once a multi-character connect response has been applied. */
+    get isMultiCharacter(): boolean;
+    /** The server-owned snapshot, or null for a single-character session. */
+    get roomSession(): ConvaiRoomSession | null;
+    find(membershipId: string): ConvaiCharacterInstance | undefined;
+    /** Members that have sent their own `bot-ready`. */
+    get readyCharacters(): ConvaiCharacterInstance[];
+    /**
+     * Mark a member ready from its own `bot-ready`, filling in any detail the
+     * connect response did not yet have.
+     *
+     * Returns whether anything changed, so the caller only pushes state when it
+     * did. A single-character `bot-ready` also carries these fields, so nothing
+     * is tracked until a roster is actually seeded.
+     */
+    applyBotReady(about: Record<string, unknown> | undefined): boolean;
+    /**
+     * Apply a `character-status` transition. Readiness recorded here is
+     * bookkeeping for replacement selection; `bot-ready` remains what gates
+     * interaction.
+     */
+    applyCharacterStatus(status: {
+        membershipId: string;
+        status: "starting" | "ready" | "failed";
+        failureCode: string | null;
+    }): boolean;
+    /**
+     * Pick a member to take over routing when the active one is removed.
+     *
+     * The runtime refuses a replacement that has not sent `bot-ready`
+     * (`replacement_target_unavailable`), so ready survivors come first. Falling
+     * back to any survivor at least produces a nameable rejection rather than
+     * `replacement_target_required`.
+     */
+    pickReplacement(removing: string[]): string | undefined;
+    /** Payload that switches the active member. */
+    buildInteractionTarget(membershipId: string | null, commandId: string): Record<string, unknown>;
+    /** Payload that adds and removes members. */
+    buildRosterUpdate(options: UpdateCharacterRosterOptions, commandId: string): Record<string, unknown>;
+    /**
+     * Adopt the server's authoritative epochs and active member from any
+     * response, errors included.
+     *
+     * A `stale_route_epoch` rejection carries the real epoch, and adopting it is
+     * precisely what makes the single retry meaningful rather than a repeat of
+     * the same losing bet.
+     */
+    adoptEpochs(extras: ServerResponseExtras | null | undefined): void;
+    /**
+     * Apply a successful `interaction-target` ack. Returns the change even when
+     * the target did not move, so a caller awaiting the promise always learns the
+     * authoritative state.
+     */
+    applyInteractionTarget(extras: ServerResponseExtras | null | undefined): ActiveCharacterChange;
+    /** Apply a successful `character-roster-update` ack, mutating the roster. */
+    applyRosterUpdate(extras: ServerResponseExtras | null | undefined): CharacterRosterChange;
+    reset(): void;
+    /**
+     * Seed the roster from a `/connect` response, for either a create or a join.
+     *
+     * Returns false for a response with no `characters` array — that is an
+     * ordinary single-character session, and the roster stays empty so
+     * `isMultiCharacter` keeps distinguishing the two.
+     */
+    applyConnectResponse(data: Record<string, unknown>): boolean;
+}
+//# sourceMappingURL=CharacterRoster.d.ts.map

package/dist/core/CharacterRoster.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"CharacterRoster.d.ts","sourceRoot":"","sources":["../../src/core/CharacterRoster.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EACV,qBAAqB,EAErB,qBAAqB,EACrB,uBAAuB,EAEvB,iBAAiB,EACjB,oBAAoB,EACpB,4BAA4B,EAC7B,MAAM,SAAS,CAAC;AA8EjB,qBAAa,eAAe;IAC1B,OAAO,CAAC,WAAW,CAAiC;IACpD,OAAO,CAAC,mBAAmB,CAAuB;IAClD,OAAO,CAAC,cAAc,CAAuB;IAC7C,OAAO,CAAC,SAAS,CAAuB;IACxC,OAAO,CAAC,eAAe,CAAuB;IAC9C,OAAO,CAAC,WAAW,CAAK;IACxB,OAAO,CAAC,YAAY,CAAK;IACzB,OAAO,CAAC,gBAAgB,CAAS;IAEjC,2EAA2E;IAC3E,IAAI,UAAU,IAAI,uBAAuB,EAAE,CAE1C;IAED,0DAA0D;IAC1D,IAAI,kBAAkB,IAAI,MAAM,GAAG,IAAI,CAEtC;IAED,IAAI,aAAa,IAAI,MAAM,GAAG,IAAI,CAEjC;IAED,IAAI,UAAU,IAAI,MAAM,CAEvB;IAED,IAAI,WAAW,IAAI,MAAM,CAExB;IAED,qEAAqE;IACrE,IAAI,gBAAgB,IAAI,OAAO,CAE9B;IAED,yEAAyE;IACzE,IAAI,WAAW,IAAI,iBAAiB,GAAG,IAAI,CAY1C;IAED,IAAI,CAAC,YAAY,EAAE,MAAM,GAAG,uBAAuB,GAAG,SAAS;IAI/D,oDAAoD;IACpD,IAAI,eAAe,IAAI,uBAAuB,EAAE,CAE/C;IAED;;;;;;;OAOG;IACH,aAAa,CAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,GAAG,OAAO;IAyClE;;;;OAIG;IACH,oBAAoB,CAAC,MAAM,EAAE;QAC3B,YAAY,EAAE,MAAM,CAAC;QACrB,MAAM,EAAE,UAAU,GAAG,OAAO,GAAG,QAAQ,CAAC;QACxC,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;KAC5B,GAAG,OAAO;IAiCX;;;;;;;OAOG;IACH,eAAe,CAAC,QAAQ,EAAE,MAAM,EAAE,GAAG,MAAM,GAAG,SAAS;IAUvD,+CAA+C;IAC/C,sBAAsB,CACpB,YAAY,EAAE,MAAM,GAAG,IAAI,EAC3B,SAAS,EAAE,MAAM,GAChB,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IAS1B,6CAA6C;IAC7C,iBAAiB,CACf,OAAO,EAAE,4BAA4B,EACrC,SAAS,EAAE,MAAM,GAChB,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC;IAmB1B;;;;;;;OAOG;IACH,WAAW,CAAC,MAAM,EAAE,oBAAoB,GAAG,IAAI,GAAG,SAAS,GAAG,IAAI;IASlE;;;;OAIG;IACH,sBAAsB,CACpB,MAAM,EAAE,oBAAoB,GAAG,IAAI,GAAG,SAAS,GAC9C,qBAAqB;IAaxB,6EAA6E;IAC7E,iBAAiB,CACf,MAAM,EAAE,oBAAoB,GAAG,IAAI,GAAG,SAAS,GAC9C,qBAAqB;IAuDxB,KAAK,IAAI,IAAI;IAWb;;;;;;OAMG;IACH,oBAAoB,CAAC,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,OAAO;CA2B7D"}