@teaflask/assistant 0.3.0 → 0.6.0

package/dist/generated/serving.d.ts

@@ -1,201 +1,38 @@
-/**
- * Generated by orval 🍺
- * Do not edit manually.
- * teaflask-serving
- * OpenAPI spec version: 1
- */
-import type { AssistantConfigResponse, CreateDeviceAuthorizationResponse, CreateServingAttachmentUploadRequest, CreateServingAttachmentUploadResponse, CurrentVisitorResponse, GetServingAssistantThreadParams, ListServingAssistantThreadsParams, MintVisitorTokenRequest, MintVisitorTokenResponse, PollDeviceAuthorizationRequest, PollDeviceAuthorizationResponse, ResolveServingTurnApprovalRequest, ResolveServingTurnApprovalResponse, ResolveServingTurnToolResultsRequest, ResolveServingTurnToolResultsResponse, SendServingAssistantMessageRequest, SendServingAssistantMessageResponse, ServingAgentDispatchResponse, ServingAssistantThreadDetailResponse, ServingAssistantThreadResponse, ServingAttachmentDownloadUrlResponse, ServingAttachmentResponse, ServingSubscriptionsResponse, StopServingTurnResponse, SubscriptionProvider } from "./models/index.js";
+import type { AssistantConfigResponse, BeginSubscriptionAuthorizationResponse, CompleteSubscriptionAuthorizationRequest, CompleteSubscriptionAuthorizationResponse, CreateServingAttachmentUploadRequest, CreateServingAttachmentUploadResponse, CurrentVisitorResponse, GetServingAssistantThreadParams, ListServingAssistantThreadsParams, MintVisitorTokenRequest, MintVisitorTokenResponse, ResolveServingTurnApprovalRequest, ResolveServingTurnApprovalResponse, ResolveServingTurnToolResultsRequest, ResolveServingTurnToolResultsResponse, SendServingAssistantMessageRequest, SendServingAssistantMessageResponse, ServingAgentDispatchResponse, ServingAssistantThreadDetailResponse, ServingAssistantThreadResponse, ServingAttachmentDownloadUrlResponse, ServingAttachmentResponse, ServingSubscriptionStatus, ServingSubscriptionsResponse, StopServingTurnResponse, SubscriptionProvider } from "./models/index.js";
 import { servingFetch } from "../transport/serving-fetch.js";
 export declare const getMintVisitorTokenUrl: () => string;
-/**
- * @summary Mint Visitor Token
- */
 export declare const mintVisitorToken: (mintVisitorTokenRequest: MintVisitorTokenRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<MintVisitorTokenResponse>;
 export declare const getReadCurrentVisitorUrl: () => string;
-/**
- * The identity plane's contract exerciser: the widget's session
- * self-check and the definition-of-done probe, until the wave-2
- * assistant endpoints become the plane's real consumers.
- * @summary Read Current Visitor
- */
 export declare const readCurrentVisitor: (options?: Parameters<typeof servingFetch>[1]) => Promise<CurrentVisitorResponse>;
 export declare const getReadAssistantConfigUrl: () => string;
-/**
- * The widget's authored configuration, resolved exactly like a turn:
- * the minting key's selected agent, else the organization's published
- * assistant, else the built-in default.
- * @summary Read Assistant Config
- */
 export declare const readAssistantConfig: (options?: Parameters<typeof servingFetch>[1]) => Promise<AssistantConfigResponse>;
 export declare const getSendServingAssistantMessageUrl: () => string;
-/**
- * Create-or-continue the visitor's conversation and start this
- * message's turn workflow — the dashboard send, under the serving trust
- * context. The turn spend is counted before anything else: turns are
- * model calls, so they carry their own small per-IP window beside the
- * blanket — per address, not per visitor, because a fresh token is a
- * fresh visitor id but never a fresh address. A message sent
- * while the previous turn still runs QUEUES (the inbox is the
- * queue, durable and ordered — the busy 409 has no producer left); a
- * parked previous turn is voided at the entity's member open — its
- * pending work superseded with the outcome recorded as unknown, one
- * beat after the 201; an unreachable orchestration
- * service settles the turn failed honestly before the 503 — never a
- * message that silently goes nowhere.
- * @summary Send Serving Assistant Message
- */
 export declare const sendServingAssistantMessage: (sendServingAssistantMessageRequest: SendServingAssistantMessageRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<SendServingAssistantMessageResponse>;
 export declare const getListServingAssistantThreadsUrl: (params?: ListServingAssistantThreadsParams) => string;
-/**
- * The identified visitor's cross-device history, most recently
- * touched first. Page with the last row's updated_at and id as
- * before_updated_at/before_id; a full page means more may exist. An
- * anonymous visitor's only handle on a conversation is its thread id, so
- * the list is empty — one widget code path, nothing enumerable to leak.
- * @summary List Serving Assistant Threads
- */
 export declare const listServingAssistantThreads: (params?: ListServingAssistantThreadsParams, options?: Parameters<typeof servingFetch>[1]) => Promise<ServingAssistantThreadResponse[]>;
 export declare const getGetServingAssistantThreadUrl: (threadId: string, params?: GetServingAssistantThreadParams) => string;
-/**
- * The conversation and the newest window of its turns (oldest-first
- * within the window), under the visitor's owner scope. Page backwards
- * with the oldest held turn's created_at and id as
- * before_created_at/before_id; a full window means earlier turns may
- * exist. Turn rows are the display source for user text — user_message
- * stores the bare message, never the LLM-side injected context.
- * @summary Get Serving Assistant Thread
- */
 export declare const getServingAssistantThread: (threadId: string, params?: GetServingAssistantThreadParams, options?: Parameters<typeof servingFetch>[1]) => Promise<ServingAssistantThreadDetailResponse>;
 export declare const getListServingAssistantThreadDispatchesUrl: (threadId: string) => string;
-/**
- * The conversation's coworker family in dispatch order, under the
- * visitor's owner scope — the widget transcript's join between its
- * dispatch receipts and the ledger, so a child that outlives its turn
- * reads settled instead of spinning. The family is thread-scoped:
- * assistant turns stamp the thread's session id as the parent, so one
- * read spans every turn. A bare array, deliberately not a keyset page —
- * and deliberately unbounded: each turn's fan-out is capped by the
- * parent's slot budget, but the family grows with every delegating
- * turn, and a newest-N bound would strand older rendered receipts
- * un-joined — a frozen launched receipt with no ledger row reads running
- * forever and keeps the widget polling indefinitely, the exact failure
- * this read exists to end. Revisit with a receipt-scoped read if
- * long-lived widget threads delegate heavily.
- * @summary List Serving Assistant Thread Dispatches
- */
 export declare const listServingAssistantThreadDispatches: (threadId: string, options?: Parameters<typeof servingFetch>[1]) => Promise<ServingAgentDispatchResponse[]>;
 export declare const getResolveServingAssistantTurnApprovalUrl: (threadId: string, turnId: string) => string;
-/**
- * Answer a paused turn's pending approvals — the dashboard's
- * record-then-wake delivery, owner-scoped to the visitor. The answers
- * land as durable rows, then the thread's ConversationWorkflow routes
- * them: couriered to a live pause, or consumed by the resume it opens
- * for a parked turn (its wait expired) — the answer still counts until
- * a new message voids it, and one already past this door answers a
- * receipt (already_consumed): the turn's own once a resume consumed it,
- * or a coworker's once its row left paused with the decision recorded —
- * however it left, or paused again at a newer round. Interrupt ids are
- * deliberately unvalidated here: an id the pause never raised satisfies
- * nothing.
- * @summary Resolve Serving Assistant Turn Approval
- */
 export declare const resolveServingAssistantTurnApproval: (threadId: string, turnId: string, resolveServingTurnApprovalRequest: ResolveServingTurnApprovalRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<ResolveServingTurnApprovalResponse>;
 export declare const getResolveServingAssistantTurnToolResultsUrl: (threadId: string, turnId: string) => string;
-/**
- * Deliver a paused turn's client-executed tool results — the
- * execution twin of the approval endpoint, owner-scoped to the visitor.
- * Every result passes the door's gate first: the size cap, validation
- * against the kind the server's own request card declared, and the
- * sanitizer pass — client-posted results are the most injection-prone
- * input this system ingests.
- *
- * While the turn is still answerable (awaiting input, or parked — a
- * parked turn restarts from the persisted session), everything posted
- * delivers: a duplicate is harmless there (the workflow's own
- * first-wins map arbitrates, and the resume answers only interrupts
- * the session still awaits), and a delivered-but-never-consumed result
- * dies with its workflow — the re-POST IS the recovery, so the door
- * must never swallow it. The receipt ledger answers only turns that
- * stopped being answerable: a voided turn records the report as
- * evidence — the only witness of a mutating action's actual outcome —
- * and a settled turn's known interrupts no-op; both say do-not-retry.
- * @summary Resolve Serving Assistant Turn Tool Results
- */
 export declare const resolveServingAssistantTurnToolResults: (threadId: string, turnId: string, resolveServingTurnToolResultsRequest: ResolveServingTurnToolResultsRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<ResolveServingTurnToolResultsResponse>;
 export declare const getStopServingAssistantTurnUrl: (threadId: string) => string;
-/**
- * End the thread's live turn as a quiet receipt — the dashboard's
- * stop door, owner-scoped to the visitor. The thread pointer names the
- * live turn (recency is not liveness: a late answer can revive a
- * parked turn behind a newer settled row); the newest row answers only
- * when no workflow holds the thread. One path: record
- * the stop intent durably, wake the live lane, and wake the thread's
- * ConversationWorkflow — the courier and the settler. Stopping an
- * already-settled turn answers a receipt, never an error: the button
- * races the answer by nature. Stop ends the turn, not the
- * conversation: the next message queues a fresh turn against the same
- * persisted session.
- * @summary Stop Serving Assistant Turn
- */
 export declare const stopServingAssistantTurn: (threadId: string, options?: Parameters<typeof servingFetch>[1]) => Promise<StopServingTurnResponse>;
 export declare const getCreateServingAttachmentUploadUrl: () => string;
-/**
- * Step one: declare the file, get back the attachment id and the
- * presigned PUT. Both storage-spend windows are counted before anything
- * is written — per address (a re-minted token never sheds one) and per
- * organization per day.
- * @summary Create Serving Attachment Upload
- */
 export declare const createServingAttachmentUpload: (createServingAttachmentUploadRequest: CreateServingAttachmentUploadRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<CreateServingAttachmentUploadResponse>;
 export declare const getFinalizeServingAttachmentUrl: (attachmentId: string) => string;
-/**
- * Step two, after the PUT: verify the object arrived, sniff what it
- * actually is, enforce its kind's size cap, flip the row ready.
- * Idempotent — a replayed finalize reads the settled row back.
- * @summary Finalize Serving Attachment
- */
 export declare const finalizeServingAttachment: (attachmentId: string, options?: Parameters<typeof servingFetch>[1]) => Promise<ServingAttachmentResponse>;
 export declare const getGetServingAttachmentDownloadUrlUrl: (attachmentId: string) => string;
-/**
- * The render-time exchange, owner-scoped exactly like the threads:
- * the visitor reads their own uploads and the attachments of
- * conversations they may open — an identified visitor their vouched
- * threads', an anonymous visitor unowned same-org threads' (knowledge
- * of the id is the capability). Everything else answers the one 404.
- * @summary Get Serving Attachment Download Url
- */
 export declare const getServingAttachmentDownloadUrl: (attachmentId: string, options?: Parameters<typeof servingFetch>[1]) => Promise<ServingAttachmentDownloadUrlResponse>;
 export declare const getListServingSubscriptionsUrl: () => string;
-/**
- * Every provider's standing for this visitor — the connect panel's
- * one read. Reports the offered axis rather than refusing on it: the
- * panel needs "not offered" as a fact, not an error.
- * @summary List Serving Subscriptions
- */
 export declare const listServingSubscriptions: (options?: Parameters<typeof servingFetch>[1]) => Promise<ServingSubscriptionsResponse>;
-export declare const getCreateDeviceAuthorizationUrl: (provider: SubscriptionProvider) => string;
-/**
- * Begin one device authorization: mint the provider's user code and
- * hand the flow back as a sealed handle. Nothing is stored — an
- * abandoned flow costs nothing and expires inside its own handle.
- * @summary Create Device Authorization
- */
-export declare const createDeviceAuthorization: (provider: SubscriptionProvider, options?: Parameters<typeof servingFetch>[1]) => Promise<CreateDeviceAuthorizationResponse>;
-export declare const getPollDeviceAuthorizationUrl: (provider: SubscriptionProvider) => string;
-/**
- * One poll of the provider's token door. On approval this is the
- * moment the credential is born: seal, store VERIFYING, start the
- * probe — the raw tokens exist in this process only for the duration
- * of the seal (billing's paste door is the sibling).
- * @summary Poll Device Authorization
- */
-export declare const pollDeviceAuthorization: (provider: SubscriptionProvider, pollDeviceAuthorizationRequest: PollDeviceAuthorizationRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<PollDeviceAuthorizationResponse>;
+export declare const getBeginSubscriptionAuthorizationUrl: (provider: SubscriptionProvider) => string;
+export declare const beginSubscriptionAuthorization: (provider: SubscriptionProvider, options?: Parameters<typeof servingFetch>[1]) => Promise<BeginSubscriptionAuthorizationResponse>;
+export declare const getCompleteSubscriptionAuthorizationUrl: (provider: SubscriptionProvider) => string;
+export declare const completeSubscriptionAuthorization: (provider: SubscriptionProvider, completeSubscriptionAuthorizationRequest: CompleteSubscriptionAuthorizationRequest, options?: Parameters<typeof servingFetch>[1]) => Promise<CompleteSubscriptionAuthorizationResponse>;
+export declare const getRecheckSubscriptionUrl: (provider: SubscriptionProvider) => string;
+export declare const recheckSubscription: (provider: SubscriptionProvider, options?: Parameters<typeof servingFetch>[1]) => Promise<ServingSubscriptionStatus>;
 export declare const getDisconnectSubscriptionUrl: (provider: SubscriptionProvider) => string;
-/**
- * Disconnects entirely — the row goes, no sealed token set lingers.
- * Deliberately no offered check: an org withdrawing the offer must
- * never strand a visitor's stored credential.
- * @summary Disconnect Subscription
- */
 export declare const disconnectSubscription: (provider: SubscriptionProvider, options?: Parameters<typeof servingFetch>[1]) => Promise<void>;
-//# sourceMappingURL=serving.d.ts.map

package/dist/generated/serving.js

@@ -2,9 +2,6 @@ import { servingFetch } from "../transport/serving-fetch.js";
 export const getMintVisitorTokenUrl = () => {
     return `/serving/v1/visitor-tokens`;
 };
-/**
- * @summary Mint Visitor Token
- */
 export const mintVisitorToken = async (mintVisitorTokenRequest, options) => {
     const getHeaders = (h) => {
         if (!h)
@@ -28,12 +25,6 @@ export const mintVisitorToken = async (mintVisitorTokenRequest, options) => {
 export const getReadCurrentVisitorUrl = () => {
     return `/serving/v1/whoami`;
 };
-/**
- * The identity plane's contract exerciser: the widget's session
- * self-check and the definition-of-done probe, until the wave-2
- * assistant endpoints become the plane's real consumers.
- * @summary Read Current Visitor
- */
 export const readCurrentVisitor = async (options) => {
     return servingFetch(getReadCurrentVisitorUrl(), {
         ...options,
@@ -43,12 +34,6 @@ export const readCurrentVisitor = async (options) => {
 export const getReadAssistantConfigUrl = () => {
     return `/serving/v1/assistant-config`;
 };
-/**
- * The widget's authored configuration, resolved exactly like a turn:
- * the minting key's selected agent, else the organization's published
- * assistant, else the built-in default.
- * @summary Read Assistant Config
- */
 export const readAssistantConfig = async (options) => {
     return servingFetch(getReadAssistantConfigUrl(), {
         ...options,
@@ -58,22 +43,6 @@ export const readAssistantConfig = async (options) => {
 export const getSendServingAssistantMessageUrl = () => {
     return `/serving/v1/assistant-threads/messages`;
 };
-/**
- * Create-or-continue the visitor's conversation and start this
- * message's turn workflow — the dashboard send, under the serving trust
- * context. The turn spend is counted before anything else: turns are
- * model calls, so they carry their own small per-IP window beside the
- * blanket — per address, not per visitor, because a fresh token is a
- * fresh visitor id but never a fresh address. A message sent
- * while the previous turn still runs QUEUES (the inbox is the
- * queue, durable and ordered — the busy 409 has no producer left); a
- * parked previous turn is voided at the entity's member open — its
- * pending work superseded with the outcome recorded as unknown, one
- * beat after the 201; an unreachable orchestration
- * service settles the turn failed honestly before the 503 — never a
- * message that silently goes nowhere.
- * @summary Send Serving Assistant Message
- */
 export const sendServingAssistantMessage = async (sendServingAssistantMessageRequest, options) => {
     const getHeaders = (h) => {
         if (!h)
@@ -106,14 +75,6 @@ export const getListServingAssistantThreadsUrl = (params) => {
         ? `/serving/v1/assistant-threads?${stringifiedParams}`
         : `/serving/v1/assistant-threads`;
 };
-/**
- * The identified visitor's cross-device history, most recently
- * touched first. Page with the last row's updated_at and id as
- * before_updated_at/before_id; a full page means more may exist. An
- * anonymous visitor's only handle on a conversation is its thread id, so
- * the list is empty — one widget code path, nothing enumerable to leak.
- * @summary List Serving Assistant Threads
- */
 export const listServingAssistantThreads = async (params, options) => {
     return servingFetch(getListServingAssistantThreadsUrl(params), {
         ...options,
@@ -132,15 +93,6 @@ export const getGetServingAssistantThreadUrl = (threadId, params) => {
         ? `/serving/v1/assistant-threads/${threadId}?${stringifiedParams}`
         : `/serving/v1/assistant-threads/${threadId}`;
 };
-/**
- * The conversation and the newest window of its turns (oldest-first
- * within the window), under the visitor's owner scope. Page backwards
- * with the oldest held turn's created_at and id as
- * before_created_at/before_id; a full window means earlier turns may
- * exist. Turn rows are the display source for user text — user_message
- * stores the bare message, never the LLM-side injected context.
- * @summary Get Serving Assistant Thread
- */
 export const getServingAssistantThread = async (threadId, params, options) => {
     return servingFetch(getGetServingAssistantThreadUrl(threadId, params), {
         ...options,
@@ -150,22 +102,6 @@ export const getServingAssistantThread = async (threadId, params, options) => {
 export const getListServingAssistantThreadDispatchesUrl = (threadId) => {
     return `/serving/v1/assistant-threads/${threadId}/dispatches`;
 };
-/**
- * The conversation's coworker family in dispatch order, under the
- * visitor's owner scope — the widget transcript's join between its
- * dispatch receipts and the ledger, so a child that outlives its turn
- * reads settled instead of spinning. The family is thread-scoped:
- * assistant turns stamp the thread's session id as the parent, so one
- * read spans every turn. A bare array, deliberately not a keyset page —
- * and deliberately unbounded: each turn's fan-out is capped by the
- * parent's slot budget, but the family grows with every delegating
- * turn, and a newest-N bound would strand older rendered receipts
- * un-joined — a frozen launched receipt with no ledger row reads running
- * forever and keeps the widget polling indefinitely, the exact failure
- * this read exists to end. Revisit with a receipt-scoped read if
- * long-lived widget threads delegate heavily.
- * @summary List Serving Assistant Thread Dispatches
- */
 export const listServingAssistantThreadDispatches = async (threadId, options) => {
     return servingFetch(getListServingAssistantThreadDispatchesUrl(threadId), {
         ...options,
@@ -175,20 +111,6 @@ export const listServingAssistantThreadDispatches = async (threadId, options) =>
 export const getResolveServingAssistantTurnApprovalUrl = (threadId, turnId) => {
     return `/serving/v1/assistant-threads/${threadId}/turns/${turnId}/approval`;
 };
-/**
- * Answer a paused turn's pending approvals — the dashboard's
- * record-then-wake delivery, owner-scoped to the visitor. The answers
- * land as durable rows, then the thread's ConversationWorkflow routes
- * them: couriered to a live pause, or consumed by the resume it opens
- * for a parked turn (its wait expired) — the answer still counts until
- * a new message voids it, and one already past this door answers a
- * receipt (already_consumed): the turn's own once a resume consumed it,
- * or a coworker's once its row left paused with the decision recorded —
- * however it left, or paused again at a newer round. Interrupt ids are
- * deliberately unvalidated here: an id the pause never raised satisfies
- * nothing.
- * @summary Resolve Serving Assistant Turn Approval
- */
 export const resolveServingAssistantTurnApproval = async (threadId, turnId, resolveServingTurnApprovalRequest, options) => {
     const getHeaders = (h) => {
         if (!h)
@@ -212,26 +134,6 @@ export const resolveServingAssistantTurnApproval = async (threadId, turnId, reso
 export const getResolveServingAssistantTurnToolResultsUrl = (threadId, turnId) => {
     return `/serving/v1/assistant-threads/${threadId}/turns/${turnId}/tool-results`;
 };
-/**
- * Deliver a paused turn's client-executed tool results — the
- * execution twin of the approval endpoint, owner-scoped to the visitor.
- * Every result passes the door's gate first: the size cap, validation
- * against the kind the server's own request card declared, and the
- * sanitizer pass — client-posted results are the most injection-prone
- * input this system ingests.
- *
- * While the turn is still answerable (awaiting input, or parked — a
- * parked turn restarts from the persisted session), everything posted
- * delivers: a duplicate is harmless there (the workflow's own
- * first-wins map arbitrates, and the resume answers only interrupts
- * the session still awaits), and a delivered-but-never-consumed result
- * dies with its workflow — the re-POST IS the recovery, so the door
- * must never swallow it. The receipt ledger answers only turns that
- * stopped being answerable: a voided turn records the report as
- * evidence — the only witness of a mutating action's actual outcome —
- * and a settled turn's known interrupts no-op; both say do-not-retry.
- * @summary Resolve Serving Assistant Turn Tool Results
- */
 export const resolveServingAssistantTurnToolResults = async (threadId, turnId, resolveServingTurnToolResultsRequest, options) => {
     const getHeaders = (h) => {
         if (!h)
@@ -255,20 +157,6 @@ export const resolveServingAssistantTurnToolResults = async (threadId, turnId, r
 export const getStopServingAssistantTurnUrl = (threadId) => {
     return `/serving/v1/assistant-threads/${threadId}/stop`;
 };
-/**
- * End the thread's live turn as a quiet receipt — the dashboard's
- * stop door, owner-scoped to the visitor. The thread pointer names the
- * live turn (recency is not liveness: a late answer can revive a
- * parked turn behind a newer settled row); the newest row answers only
- * when no workflow holds the thread. One path: record
- * the stop intent durably, wake the live lane, and wake the thread's
- * ConversationWorkflow — the courier and the settler. Stopping an
- * already-settled turn answers a receipt, never an error: the button
- * races the answer by nature. Stop ends the turn, not the
- * conversation: the next message queues a fresh turn against the same
- * persisted session.
- * @summary Stop Serving Assistant Turn
- */
 export const stopServingAssistantTurn = async (threadId, options) => {
     return servingFetch(getStopServingAssistantTurnUrl(threadId), {
         ...options,
@@ -278,13 +166,6 @@ export const stopServingAssistantTurn = async (threadId, options) => {
 export const getCreateServingAttachmentUploadUrl = () => {
     return `/serving/v1/assistant-attachments`;
 };
-/**
- * Step one: declare the file, get back the attachment id and the
- * presigned PUT. Both storage-spend windows are counted before anything
- * is written — per address (a re-minted token never sheds one) and per
- * organization per day.
- * @summary Create Serving Attachment Upload
- */
 export const createServingAttachmentUpload = async (createServingAttachmentUploadRequest, options) => {
     const getHeaders = (h) => {
         if (!h)
@@ -308,12 +189,6 @@ export const createServingAttachmentUpload = async (createServingAttachmentUploa
 export const getFinalizeServingAttachmentUrl = (attachmentId) => {
     return `/serving/v1/assistant-attachments/${attachmentId}/finalize`;
 };
-/**
- * Step two, after the PUT: verify the object arrived, sniff what it
- * actually is, enforce its kind's size cap, flip the row ready.
- * Idempotent — a replayed finalize reads the settled row back.
- * @summary Finalize Serving Attachment
- */
 export const finalizeServingAttachment = async (attachmentId, options) => {
     return servingFetch(getFinalizeServingAttachmentUrl(attachmentId), {
         ...options,
@@ -323,14 +198,6 @@ export const finalizeServingAttachment = async (attachmentId, options) => {
 export const getGetServingAttachmentDownloadUrlUrl = (attachmentId) => {
     return `/serving/v1/assistant-attachments/${attachmentId}/download-url`;
 };
-/**
- * The render-time exchange, owner-scoped exactly like the threads:
- * the visitor reads their own uploads and the attachments of
- * conversations they may open — an identified visitor their vouched
- * threads', an anonymous visitor unowned same-org threads' (knowledge
- * of the id is the capability). Everything else answers the one 404.
- * @summary Get Serving Attachment Download Url
- */
 export const getServingAttachmentDownloadUrl = async (attachmentId, options) => {
     return servingFetch(getGetServingAttachmentDownloadUrlUrl(attachmentId), {
         ...options,
@@ -340,44 +207,25 @@ export const getServingAttachmentDownloadUrl = async (attachmentId, options) =>
 export const getListServingSubscriptionsUrl = () => {
     return `/serving/v1/subscriptions`;
 };
-/**
- * Every provider's standing for this visitor — the connect panel's
- * one read. Reports the offered axis rather than refusing on it: the
- * panel needs "not offered" as a fact, not an error.
- * @summary List Serving Subscriptions
- */
 export const listServingSubscriptions = async (options) => {
     return servingFetch(getListServingSubscriptionsUrl(), {
         ...options,
         method: "GET",
     });
 };
-export const getCreateDeviceAuthorizationUrl = (provider) => {
-    return `/serving/v1/subscriptions/${provider}/device-authorizations`;
-};
-/**
- * Begin one device authorization: mint the provider's user code and
- * hand the flow back as a sealed handle. Nothing is stored — an
- * abandoned flow costs nothing and expires inside its own handle.
- * @summary Create Device Authorization
- */
-export const createDeviceAuthorization = async (provider, options) => {
-    return servingFetch(getCreateDeviceAuthorizationUrl(provider), {
+export const getBeginSubscriptionAuthorizationUrl = (provider) => {
+    return `/serving/v1/subscriptions/${provider}/authorizations`;
+};
+export const beginSubscriptionAuthorization = async (provider, options) => {
+    return servingFetch(getBeginSubscriptionAuthorizationUrl(provider), {
         ...options,
         method: "POST",
     });
 };
-export const getPollDeviceAuthorizationUrl = (provider) => {
-    return `/serving/v1/subscriptions/${provider}/device-authorizations/poll`;
-};
-/**
- * One poll of the provider's token door. On approval this is the
- * moment the credential is born: seal, store VERIFYING, start the
- * probe — the raw tokens exist in this process only for the duration
- * of the seal (billing's paste door is the sibling).
- * @summary Poll Device Authorization
- */
-export const pollDeviceAuthorization = async (provider, pollDeviceAuthorizationRequest, options) => {
+export const getCompleteSubscriptionAuthorizationUrl = (provider) => {
+    return `/serving/v1/subscriptions/${provider}/authorizations/complete`;
+};
+export const completeSubscriptionAuthorization = async (provider, completeSubscriptionAuthorizationRequest, options) => {
     const getHeaders = (h) => {
         if (!h)
             return {};
@@ -387,29 +235,31 @@ export const pollDeviceAuthorization = async (provider, pollDeviceAuthorizationR
             return Object.fromEntries(h);
         return h;
     };
-    return servingFetch(getPollDeviceAuthorizationUrl(provider), {
+    return servingFetch(getCompleteSubscriptionAuthorizationUrl(provider), {
         ...options,
         method: "POST",
         headers: {
             "Content-Type": "application/json",
             ...getHeaders(options?.headers),
         },
-        body: JSON.stringify(pollDeviceAuthorizationRequest),
+        body: JSON.stringify(completeSubscriptionAuthorizationRequest),
+    });
+};
+export const getRecheckSubscriptionUrl = (provider) => {
+    return `/serving/v1/subscriptions/${provider}/recheck`;
+};
+export const recheckSubscription = async (provider, options) => {
+    return servingFetch(getRecheckSubscriptionUrl(provider), {
+        ...options,
+        method: "POST",
     });
 };
 export const getDisconnectSubscriptionUrl = (provider) => {
     return `/serving/v1/subscriptions/${provider}`;
 };
-/**
- * Disconnects entirely — the row goes, no sealed token set lingers.
- * Deliberately no offered check: an org withdrawing the offer must
- * never strand a visitor's stored credential.
- * @summary Disconnect Subscription
- */
 export const disconnectSubscription = async (provider, options) => {
     return servingFetch(getDisconnectSubscriptionUrl(provider), {
         ...options,
         method: "DELETE",
     });
 };
-//# sourceMappingURL=serving.js.map

package/dist/headless.d.ts

@@ -1,4 +1,4 @@
-export { TeaflaskAssistantProvider, type TeaflaskAssistantProviderProps, } from "./components/teaflask-assistant-provider.js";
+export { TeaflaskAssistantProvider, type TeaflaskAssistantAnonymousProps, type TeaflaskAssistantIdentityProps, type TeaflaskAssistantProviderBaseProps, type TeaflaskAssistantProviderProps, } from "./components/teaflask-assistant-provider.js";
 export type { AssistantTheme, AssistantThemeDarkTokens, AssistantThemeMode, AssistantThemeTokens, } from "./appearance/theme.js";
 export type { ActionsAdapter, ActionIntent, ActionIntentAction, CookiesActionsAdapter, HeadersActionsAdapter, RequestActionsAdapter, } from "./contract/actions-adapter.js";
 export type { ApprovalSubmitTelemetryEvent, AssistantTelemetryEvent, StreamFailedTelemetryEvent, } from "./contract/telemetry.js";
@@ -38,4 +38,3 @@ export type { AssistantActivityResult, AssistantActivitySnapshot, } from "./core
 export type { TurnStatus } from "./contract/threads.js";
 export type { UserTurnMeta } from "./core/user-turn-ledger.js";
 export { resetAssistant } from "./persistence/stored-thread.js";
-//# sourceMappingURL=headless.d.ts.map

package/dist/headless.js

@@ -1,49 +1,10 @@
-// The bring-your-own-frontend entry: the provider and the
-// live-session hooks, with none of the package chrome. A host mounts
-// <TeaflaskAssistantProvider> alone, DRIVES the conversation through
-// useAssistantConversation()'s contract, the composer contract, and the
-// approval/elicitation surfaces, and RENDERS the replies through
-// useTranscript()'s read surface — bindings over the shared
-// store, never the machinery. The read surface lives here, not on
-// ./transcript, because binding to a live store needs the transport the
-// provider constructs; the anchor RECORDERS stay on ./transcript for
-// own-wire hosts. The serving session internals stay private on purpose;
-// tests/bundle-closure.test.ts holds this entry's static closure chrome-free.
 export { TeaflaskAssistantProvider, } from "./components/teaflask-assistant-provider.js";
 export { useAssistantConversation, } from "./components/use-assistant-conversation.js";
 export { useConversation, } from "./components/conversation-context.js";
 export { useApprovals, } from "./components/approval-context.js";
 export { useElicitations, } from "./components/elicitation-context.js";
-// The composer contract's per-keystroke half rides its own cell
-// (composerInput) so reading it never re-renders the coarse contract —
-// useCell is the one React seam onto a cell, exported so a host's own
-// composer reads it the way the package chrome does.
 export { useCell } from "./components/use-store-cell.js";
 export { ServingApiError } from "./transport/serving-error.js";
-// The transcript read surface: rendering the assistant's
-// replies from this entry. Mounting the hook registers transcript
-// presence with the store — presence is what GUARANTEES the epoch
-// connects (once, so history paints by full replay), and what arms the
-// idle re-read. A lease-less store connects only while the newest turn
-// is queued/working (bounded budget — the connection truth table in
-// core/connection-driver.ts), and that connect is the same full replay; what it
-// never gets is a connect while no turn is live, so a reopened settled
-// thread's messages stay empty without the hook.
 export { useTranscript, } from "./components/use-transcript.js";
-// The projection and its row types, re-exported from their core modules.
-// Where a name is also on ./transcript (transcriptRowsOf, TranscriptRow,
-// Message, MarkerAnchorsSnapshot, ToolCallDisplay, SubagentGroupRow,
-// SubagentGroupEntry, DispatchReceipt) it is the SAME symbol, so a host may
-// mix imports freely; the rest are public here (several row members also
-// ride ./transcript-ui). transcriptRowsOf and
-// withPendingUserEcho ride as values so a host projecting the raw reads
-// never needs a second entry; Message is re-exported so a host never takes
-// its own dependency on the @ag-ui packages.
 export { transcriptRowsOf, withPendingUserEcho, } from "./core/transcript-rows.js";
-// Sign-out belongs to a bring-your-own-frontend host too: without this,
-// the README's sign-out instruction pulls the ROOT barrel (transcript,
-// markdown and all) into a headless bundle for one localStorage helper.
-// Zero closure cost — persistence/stored-thread already rides this
-// entry via the conversation store.
 export { resetAssistant } from "./persistence/stored-thread.js";
-//# sourceMappingURL=headless.js.map

package/dist/index.d.ts

@@ -1,6 +1,6 @@
 export type { AssistantTheme, AssistantThemeDarkTokens, AssistantThemeMode, AssistantThemeTokens, } from "./appearance/theme.js";
-export { TeaflaskAssistantProvider, type TeaflaskAssistantProviderProps, } from "./components/teaflask-assistant-provider.js";
-export { TeaflaskAssistant, type TeaflaskAssistantHandle, type TeaflaskAssistantProps, } from "./components/teaflask-assistant.js";
+export { TeaflaskAssistantProvider, type TeaflaskAssistantAnonymousProps, type TeaflaskAssistantIdentityProps, type TeaflaskAssistantProviderBaseProps, type TeaflaskAssistantProviderProps, } from "./components/teaflask-assistant-provider.js";
+export { TeaflaskAssistant, type TeaflaskAssistantHandle, type TeaflaskAssistantProps, type TeaflaskAssistantRootProps, } from "./components/teaflask-assistant.js";
 export { AssistantPage, type AssistantChrome, type AssistantPageProps, } from "./components/assistant-page.js";
 export type { AssistantSuggestion, AssistantSuggestionInput, AssistantSuggestionKind, } from "./components/conversation-view.js";
 export { AssistantPalette, type AssistantPaletteProps, } from "./components/assistant-palette.js";
@@ -12,7 +12,7 @@ export { ServingApiError } from "./transport/serving-error.js";
 export type { ActionIntent, ActionIntentAction, ActionsAdapter, CookiesActionsAdapter, HeadersActionsAdapter, RequestActionsAdapter, } from "./contract/actions-adapter.js";
 export type { ServingErrorBody, ServingErrorCode, ServingErrorCodeOnTheWire, ServingErrorEnvelope, } from "./contract/errors.js";
 export type { EndUserIdentity, MintVisitorTokenRequest, MintVisitorTokenResponse, PublishableKeyMode, VisitorTier, WhoamiResponse, } from "./contract/identity.js";
-export type { SubscriptionCredentialState, SubscriptionDeviceAuthorization, SubscriptionDeviceAuthorizationPoll, SubscriptionProvider, SubscriptionStatus, } from "./contract/subscriptions.js";
+export { SUBSCRIPTION_CONNECT_MESSAGE_TYPE, subscriptionConnectMessageOf, type SubscriptionAuthorization, type SubscriptionAuthorizationCompletion, type SubscriptionAuthorizationCompletionRequest, type SubscriptionConnectMessage, type SubscriptionCredentialState, type SubscriptionProvider, type SubscriptionStatus, } from "./contract/subscriptions.js";
 export { ASSISTANT_MESSAGE_MAX_CHARS, type ApprovalDelivery, type AssistantThreadDetailResponse, type ResolveTurnApprovalRequest, type ResolveTurnApprovalResponse, type SendAssistantMessageRequest, type SendAssistantMessageResponse, type ServingAssistantThread, type ServingAssistantTurn, type TurnApprovalDecision, type TurnStatus, } from "./contract/threads.js";
 export { APPROVAL_REQUESTED_EVENT_NAME, MEMORY_UPDATED_EVENT_NAME, RUN_RESUMED_EVENT_NAME, TURN_USAGE_RECORDED_EVENT_NAME, type ApprovalRequestedPayload, type AssistantStreamEventType, type RunResumedPayload, } from "./contract/events.js";
 export { activeFoldElapsedOf, settledFoldDurationOf, type BlockTiming, type SegmentDuration, } from "./core/segment-timing.js";
@@ -26,4 +26,3 @@ export { reactToolView } from "./components/react-tool-view.js";
 export { ToolViewBadge, ToolViewBody, ToolViewBones, ToolViewScroll, ToolViewTitle, ToolViewCaption, ToolViewCard, ToolViewFacts, ToolViewNote, ToolViewRow, } from "./components/tool-views/parts.js";
 export { actionEnvelopeOf, actionFailureOf, boneRows, captionRow, card, factRows, humanFailureSentenceOf, listRow, note, pane, recordOf, scrollRegion, terminal, settledOutcomeNoteOf, settledOutcomeNotesOf, settledWithResult, type ActionEnvelope, type ActionFailure, } from "./components/tool-views/view-dom.js";
 export { AssistantCompanion, type AssistantCompanionProps, } from "./components/assistant-companion.js";
-//# sourceMappingURL=index.d.ts.map