@belonguniverseai/react-sdk 0.6.15 → 0.6.16

package/dist/stream/belong-data-parts.d.ts

@@ -15,7 +15,7 @@ export type PlanStep = {
 };
 export type ApprovalState = "pending" | "approved" | "rejected" | "amend_requested" | "expired";
 export type ToolCallState = "started" | "completed" | "failed";
-export type ChoiceState = "pending" | "resolved" | "expired";
+export type ChoiceState = "pending" | "answered" | "dismissed" | "detached" | "cancelled";
 export type SandboxCommandState = "started" | "output" | "completed" | "failed";
 export type SandboxStream = "stdout" | "stderr";
 export type UiActionState = "requested" | "completed" | "failed";
@@ -48,44 +48,51 @@ export type ApprovalRequestData = {
     readonly subagentId?: string | undefined;
 };
 /**
- * BEL-93 — a friendly question widget the agent emits instead of dumping a wall
- * of questions as prose. Discriminated on `mode`:
- *   - "single": choose exactly one option (radio group)
- *   - "multi":  choose several options (checkbox list), bounded by
- *               min/maxChoicesCount when present
- *   - "open":   free-text answer (textarea)
- * The user answers in-dock; the SDK posts the answer back through the same
- * `ui-actions/:uiActionRequestId/result` endpoint the UI-action renderer uses,
- * so no new backend route is needed. `state` mirrors the approval lifecycle
- * (see ChoiceState) so a resolved/expired question survives a reload.
+ * Plan 013 (supersedes BEL-93's single-question shape) — the agent's
+ * `AskUserQuestion` call as ONE part: 1–4 questions, each single- or
+ * multi-select with 2–4 options (label + description). The dock adds its own
+ * "Something else" free-text row and a per-question Skip. Answers post to
+ * `POST /v1/questions/:questionRequestId/answer` by option id; `answers` /
+ * `reply` are filled in by the backend on resolution (live) or by the history
+ * patch (reload) so the transcript record renders identically either way.
  */
 export type ChoiceOption = {
     readonly id: string;
     readonly label: string;
-    readonly description?: string | undefined;
+    readonly description: string;
 };
-export type ChoiceRequestData = {
-    readonly mode: "single";
-    readonly uiActionRequestId: string;
+export type ChoiceQuestion = {
+    readonly id: string;
     readonly question: string;
+    /** Chip label, ≤ 12 chars. */
+    readonly header: string;
+    readonly multiSelect: boolean;
     readonly options: readonly ChoiceOption[];
-    readonly state: ChoiceState;
+};
+/**
+ * One question's answer. On a MULTI-select question `text` alongside
+ * `optionIds` is the "Something else" free text combined with the ticks — the
+ * agent gets both. A single-select answer is exactly one option OR `text`
+ * (the server rejects options + text there).
+ */
+export type ChoiceAnswer = {
+    readonly kind: "options";
+    readonly optionIds: readonly string[];
+    readonly text?: string | undefined;
 } | {
-    readonly mode: "multi";
-    readonly uiActionRequestId: string;
-    readonly question: string;
-    readonly options: readonly ChoiceOption[];
-    readonly state: ChoiceState;
-    /** Inclusive lower bound on selected options. Absent ⇒ at least one (1). */
-    readonly minChoicesCount?: number | undefined;
-    /** Inclusive upper bound on selected options. Absent ⇒ no maximum. */
-    readonly maxChoicesCount?: number | undefined;
+    readonly kind: "text";
+    readonly text: string;
 } | {
-    readonly mode: "open";
-    readonly uiActionRequestId: string;
-    readonly question: string;
+    readonly kind: "skipped";
+};
+export type ChoiceRequestData = {
+    readonly questionRequestId: string;
     readonly state: ChoiceState;
-    readonly placeholder?: string | undefined;
+    readonly questions: readonly ChoiceQuestion[];
+    /** Keyed by question id. Present once answered. */
+    readonly answers?: Readonly<Record<string, ChoiceAnswer>> | undefined;
+    /** The composer text when the user replied in chat instead of choosing. */
+    readonly reply?: string | undefined;
 };
 /**
  * Optional fields declared with explicit `| undefined` so Zod's

package/dist/stream/pending-question-store.d.ts

@@ -0,0 +1,22 @@
+import { BelongUIMessage, ChoiceRequestData } from './belong-data-parts.ts';
+/** Snapshot — identity is stable until the set changes (useSyncExternalStore). */
+export declare const peekHiddenQuestions: () => ReadonlySet<string>;
+export declare const subscribeHiddenQuestions: (listener: () => void) => (() => void);
+export declare const isQuestionHidden: (questionRequestId: string) => boolean;
+export declare const hideQuestion: (questionRequestId: string) => void;
+export declare const unhideQuestion: (questionRequestId: string) => void;
+export declare const __resetPendingQuestionStoreForTest: () => void;
+/**
+ * The question the bottom card should show: the NEWEST answerable
+ * `data-choice-request` part across the conversation that is not hidden, or
+ * null. Same-id parts replace each other in `useChat` (a resolution arrives
+ * as the same part id with a terminal state), so a question that was answered
+ * — from this tab, another tab, or a reload's history patch — un-arms the card
+ * from the wire without any local bookkeeping.
+ *
+ * The LAST occurrence of each question id wins before "newest" is decided: a
+ * restored history part and a resumed stream's re-emit of the same question
+ * (§40 re-attach) can sit in different messages, and only the later one
+ * carries the current state.
+ */
+export declare const selectActiveQuestion: (messages: readonly BelongUIMessage[], hiddenIds: ReadonlySet<string>) => ChoiceRequestData | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@belonguniverseai/react-sdk",
-  "version": "0.6.15",
+  "version": "0.6.16",
   "description": "Belong — embeddable React AI assistant dock. Mount <BelongWidget> in your app tree with getToken dependency-injection auth.",
   "license": "UNLICENSED",
   "type": "module",