@relaymessenger/chat-sdk-adapter 0.2.0 → 0.3.0-staging.0

package/dist/src/threadId.js

@@ -1,28 +0,0 @@
-/**
- * Relay thread ids are `relay:{conversation_id}`. A Relay conversation has no
- * enclosing channel, so the channel id is the same string. Both are written
- * out here rather than left to the Chat SDK defaults, because the default
- * channel derivation keeps the first two colon-separated segments and that
- * only happens to be correct for this shape.
- */
-export const RELAY_THREAD_PREFIX = "relay:";
-export function encodeRelayThreadId(platformData) {
-    const conversationId = platformData.conversationId;
-    if (!conversationId) {
-        throw new Error("conversationId is required to encode a Relay thread id");
-    }
-    return `${RELAY_THREAD_PREFIX}${conversationId}`;
-}
-export function decodeRelayThreadId(threadId) {
-    if (!threadId.startsWith(RELAY_THREAD_PREFIX)) {
-        throw new Error(`not a Relay thread id: ${threadId}`);
-    }
-    const conversationId = threadId.slice(RELAY_THREAD_PREFIX.length);
-    if (!conversationId) {
-        throw new Error(`Relay thread id carries no conversation id: ${threadId}`);
-    }
-    return { conversationId };
-}
-export function relayChannelIdFromThreadId(threadId) {
-    return encodeRelayThreadId(decodeRelayThreadId(threadId));
-}

package/dist/src/turn.d.ts

@@ -1,38 +0,0 @@
-/**
- * What the inbound event told us about the turn now in flight. `postMessage`
- * and `startTyping` never see the event, so the invocation id a group reply
- * must echo, and the event id an idempotency key must be derived from, are
- * carried here.
- *
- * The turn rides on the async execution context of the dispatch that created
- * it rather than on a map keyed by conversation. A map is wrong: the Chat SDK
- * takes its per-thread lock inside `processMessage`, well after the adapter
- * would have written the entry, so two messages arriving together in one group
- * let the second overwrite the first's entry and then get dropped by the lock,
- * leaving the first turn replying with the second's invocation and key. A
- * context store cannot be overwritten by a sibling dispatch, and it needs no
- * cleanup, so there is nothing to grow without bound either.
- *
- * The Chat SDK already runs on `AsyncLocalStorage` for its own conversation
- * context (`chat/dist/chunk-23HOOUQ5.js:130`), so this adds no runtime
- * requirement the peer dependency did not already impose.
- */
-export interface RelayTurn {
-    /** The conversation the inbound event arrived on. */
-    readonly conversationId: string;
-    readonly eventId: string;
-    /** Present only for a group event: Relay scopes a group reply to it. */
-    readonly invocationId?: string;
-    /** Set once the invocation has been spent on a committed message. */
-    invocationUsed: boolean;
-    /** Messages this turn has committed. Advances only on a successful send. */
-    sent: number;
-}
-/** Run one inbound dispatch with its turn bound to the async context. */
-export declare function runInTurn<T>(turn: RelayTurn, fn: () => Promise<T>): Promise<T>;
-/**
- * The turn in flight, when it belongs to this conversation. A handler that
- * posts into some other conversation is not replying to the event, so it gets
- * nothing here and falls back to an unkeyed send.
- */
-export declare function activeTurn(conversationId: string): RelayTurn | undefined;

package/dist/src/turn.js

@@ -1,15 +0,0 @@
-import { AsyncLocalStorage } from "node:async_hooks";
-const storage = new AsyncLocalStorage();
-/** Run one inbound dispatch with its turn bound to the async context. */
-export function runInTurn(turn, fn) {
-    return storage.run(turn, fn);
-}
-/**
- * The turn in flight, when it belongs to this conversation. A handler that
- * posts into some other conversation is not replying to the event, so it gets
- * nothing here and falls back to an unkeyed send.
- */
-export function activeTurn(conversationId) {
-    const turn = storage.getStore();
-    return turn?.conversationId === conversationId ? turn : undefined;
-}

package/dist/src/types.d.ts

@@ -1,177 +0,0 @@
-/**
- * Wire types for the Relay v1 developer API, scoped to what this adapter
- * consumes and produces. The authoritative contract is the published OpenAPI
- * document at https://docs.relayapp.im/api-reference. The part discriminator
- * is `type`.
- */
-export interface RelayEventEnvelope<TData = unknown> {
-    event_id: string;
-    event_type: string;
-    agent_id: string;
-    created_at: string;
-    data: TData;
-}
-export interface RelaySender {
-    kind: "user" | "agent" | "system";
-    id: string;
-}
-/**
- * Inline mention of a conversation participant. Offsets are UTF-16 code units
- * into the part's `text`, which holds the inserted display name with no "@".
- * Ranges are sorted by `start` and never overlap.
- */
-export interface RelayMentionRange {
-    start: number;
-    length: number;
-    participant_id: string;
-}
-export type RelayTextStyle = "bold" | "italic" | "underline" | "strikethrough" | "monospace" | "spoiler";
-/**
- * One formatting run over a text part, offsets in UTF-16 code units like
- * mentions. An EMPTY `styles` array on the part is meaningful: it marks
- * structured plain text as opposed to a legacy Markdown body.
- */
-export interface RelayStyleRange {
-    start: number;
-    length: number;
-    styles: RelayTextStyle[];
-}
-/** Outgoing part shapes accepted by `POST /v1/messages`. */
-export type RelayOutgoingPart = {
-    type: "text";
-    text: string;
-    mentions?: RelayMentionRange[];
-    styles?: RelayStyleRange[];
-} | {
-    type: "media";
-    attachment_id?: string;
-    url?: string;
-    content_type?: string;
-} | {
-    type: "voice_memo";
-    attachment_id?: string;
-    url?: string;
-    duration_ms?: number;
-} | {
-    type: "link_preview";
-    url: string;
-    title?: string;
-    description?: string;
-} | {
-    type: "data";
-    data: Record<string, unknown>;
-};
-/** Stored canonical part as delivered in events and history. */
-export interface RelayPart {
-    type: string;
-    part_index?: number;
-    text?: string;
-    mentions?: RelayMentionRange[];
-    styles?: RelayStyleRange[];
-    url?: string;
-    attachment_id?: string;
-    content_type?: string;
-    media_kind?: "image" | "video" | "audio" | "file";
-    filename?: string;
-    size_bytes?: number;
-    duration_ms?: number;
-    width?: number;
-    height?: number;
-    blur_hash?: string;
-    title?: string;
-    description?: string;
-    data?: Record<string, unknown>;
-    [key: string]: unknown;
-}
-/**
- * A message as Relay projects it for this agent. A tombstone carries no
- * `parts`, so every reader must treat that field as optional.
- */
-export interface RelayMessage {
-    id: string;
-    conversation_id: string;
-    sequence: number;
-    sender: RelaySender;
-    is_from_me?: boolean;
-    parts?: RelayPart[];
-    reply_to?: {
-        message_id?: string;
-    } | null;
-    invoked_agents?: string[];
-    reactions?: unknown[];
-    fallback_text?: string;
-    status: string;
-    delivered_at?: string;
-    read_at?: string;
-    edited_at?: string;
-    unsent_at?: string;
-    created_at: string;
-}
-export interface RelayMessageEventData {
-    message: RelayMessage;
-    invocation_id?: string;
-}
-export interface RelayMessageUnsentEventData {
-    message_id: string;
-    conversation_id: string;
-    sequence: number;
-}
-/**
- * The 202 from `POST /v1/messages`. The server splits the accepted parts at
- * ingest: each visible non-media part becomes its own message, contiguous
- * media parts stay one media message, and a voice memo always commits alone,
- * so one send commits one or more messages, in display order.
- */
-export interface RelaySendResult {
-    messages: RelayMessage[];
-}
-export interface RelayConversation {
-    id: string;
-    kind: "direct" | "group";
-    title: string | null;
-    counterpart_user: {
-        id: string;
-        display_name: string;
-        avatar_url: string | null;
-    } | null;
-    participant_count: number;
-    last_sequence: number;
-    last_message_at: string | null;
-    created_at: string;
-}
-export interface RelayUserProfile {
-    id: string;
-    name: string;
-    first_name: string;
-    last_name: string;
-    phone_number: string | null;
-    avatar_url: string | null;
-    created_at: string;
-}
-export interface RelayAttachment {
-    id: string;
-    url: string;
-    content_type: string;
-    size_bytes: number;
-}
-/**
- * Relay carries one reaction kind. The field survives because the wire still
- * names it, not because there is a choice to make.
- */
-export type RelayReactionType = "emoji";
-/**
- * The raw payload this adapter hands to the Chat SDK. It carries the group
- * invocation id alongside the message because Relay scopes a group reply to
- * the invocation that produced the inbound event, and `Adapter.postMessage`
- * never sees the event.
- */
-export interface RelayRawMessage {
-    message: RelayMessage;
-    invocation_id?: string;
-    event_id?: string;
-    event_type?: string;
-}
-/** Platform-specific data behind a Relay thread id. */
-export interface RelayThreadId {
-    conversationId: string;
-}

package/dist/src/types.js

@@ -1,7 +0,0 @@
-/**
- * Wire types for the Relay v1 developer API, scoped to what this adapter
- * consumes and produces. The authoritative contract is the published OpenAPI
- * document at https://docs.relayapp.im/api-reference. The part discriminator
- * is `type`.
- */
-export {};