@kortexya/reasoninglayer 1.11.0 → 1.12.0

package/dist/index.cjs

@@ -7,7 +7,7 @@ var __export = (target, all) => {
 };
 
 // src/config.ts
-var SDK_VERSION = "1.11.0";
+var SDK_VERSION = "1.12.0";
 function resolveConfig(config) {
   if (!config.baseUrl) {
     throw new Error("ClientConfig.baseUrl is required");
@@ -23297,6 +23297,33 @@ var ResearchClient = class {
     });
     return ResearchSessionResponseFromApiToFront(response.data);
   }
+  /**
+   * Resume an interrupted or failed research session.
+   *
+   * A session left in a non-`Completed` state — e.g. swept to `Failed` after a
+   * server restart killed its in-process pipeline — is otherwise stuck. Resuming
+   * re-runs the pipeline, continuing from the session's persisted partial
+   * progress (papers ingested, findings, cycles), and can reach `Completed`.
+   * Like {@link runToCompletion} the run is long-lived server-side; the UI
+   * typically calls this fire-and-forget and polls {@link getSession}.
+   *
+   * @param sessionId - The session ID (UUID) to resume.
+   * @throws {ApiError} 409 if the session is already `Completed`, 404 if unknown.
+   *
+   * @example
+   * ```ts
+   * await client.research.resumeSession('session-uuid');
+   * ```
+   */
+  async resumeSession(sessionId) {
+    const response = await this.http.request({
+      path: `/api/v1/research/sessions/${encodeURIComponent(sessionId)}/resume`,
+      method: "POST",
+      secure: true,
+      format: "json"
+    });
+    return ResearchSessionResponseFromApiToFront(response.data);
+  }
   /**
    * Delete a research session and all associated data.
    *