@acedatacloud/sdk 2026.722.0 → 2026.727.1

package/dist/index.d.mts

@@ -177,7 +177,18 @@ declare class Chat {
     constructor(transport: Transport);
 }
 
-/** Task polling abstraction. */
+/**
+ * Task polling for long-running operations.
+ *
+ * A generation call always returns a handle, never sometimes a handle and
+ * sometimes a plain object — the caller decides whether to wait. When the server
+ * answers synchronously (some endpoints do for fast or cached results) the
+ * handle is born already complete, so `wait()` returns immediately rather than
+ * polling for something that has already arrived.
+ *
+ * Kept behaviourally identical to the Python and Go implementations; a
+ * divergence here is a cross-language bug that only shows up in production.
+ */
 
 interface TaskHandleOptions {
     pollInterval?: number;
@@ -188,8 +199,20 @@ declare class TaskHandle {
     private pollEndpoint;
     private transport;
     private _result;
-    constructor(taskId: string, pollEndpoint: string, transport: Transport);
+    constructor(taskId: string, pollEndpoint: string, transport: Transport, submitted?: Record<string, unknown>);
+    get done(): boolean;
+    /** Artifact URLs, once completed. */
+    urls(): string[];
+    progress(): number | null;
+    /**
+     * Fetch current task state, remembering it once terminal.
+     *
+     * A caller that drives its own poll loop — checking status between polls so it
+     * can report progress — only ever calls this. Without recording here, urls()
+     * and result() stay empty after the task has plainly finished.
+     */
     get(): Promise<Record<string, unknown>>;
+    private accept;
     isCompleted(): Promise<boolean>;
     wait(opts?: TaskHandleOptions): Promise<Record<string, unknown>>;
     get result(): Record<string, unknown> | null;

package/dist/index.d.ts

@@ -177,7 +177,18 @@ declare class Chat {
     constructor(transport: Transport);
 }
 
-/** Task polling abstraction. */
+/**
+ * Task polling for long-running operations.
+ *
+ * A generation call always returns a handle, never sometimes a handle and
+ * sometimes a plain object — the caller decides whether to wait. When the server
+ * answers synchronously (some endpoints do for fast or cached results) the
+ * handle is born already complete, so `wait()` returns immediately rather than
+ * polling for something that has already arrived.
+ *
+ * Kept behaviourally identical to the Python and Go implementations; a
+ * divergence here is a cross-language bug that only shows up in production.
+ */
 
 interface TaskHandleOptions {
     pollInterval?: number;
@@ -188,8 +199,20 @@ declare class TaskHandle {
     private pollEndpoint;
     private transport;
     private _result;
-    constructor(taskId: string, pollEndpoint: string, transport: Transport);
+    constructor(taskId: string, pollEndpoint: string, transport: Transport, submitted?: Record<string, unknown>);
+    get done(): boolean;
+    /** Artifact URLs, once completed. */
+    urls(): string[];
+    progress(): number | null;
+    /**
+     * Fetch current task state, remembering it once terminal.
+     *
+     * A caller that drives its own poll loop — checking status between polls so it
+     * can report progress — only ever calls this. Without recording here, urls()
+     * and result() stay empty after the task has plainly finished.
+     */
     get(): Promise<Record<string, unknown>>;
+    private accept;
     isCompleted(): Promise<boolean>;
     wait(opts?: TaskHandleOptions): Promise<Record<string, unknown>>;
     get result(): Record<string, unknown> | null;