@kortexya/reasoninglayer 1.11.0 → 1.12.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.cts CHANGED
@@ -109,7 +109,7 @@ type JsonValue$1 = string | number | boolean | null | JsonValue$1[] | object;
109
109
  * This is the single source of truth for the version constant.
110
110
  * The `scripts/release.sh` script updates this value alongside `package.json`.
111
111
  */
112
- declare const SDK_VERSION = "1.11.0";
112
+ declare const SDK_VERSION = "1.12.1";
113
113
  /**
114
114
  * Authentication mode for the SDK.
115
115
  *
@@ -44108,6 +44108,9 @@ interface TurnDto {
44108
44108
  osfql?: string | null;
44109
44109
  /** Per-claim provenance annotations (assistant turns only). */
44110
44110
  claimAnnotations?: ClaimAnnotationDto[] | null;
44111
+ /** MATCH result rows (assistant turns only), persisted by the backend so a
44112
+ * "show me a table of X" answer keeps its table across a reload. */
44113
+ queryResults?: Record<string, OsfqlValue>[] | null;
44111
44114
  }
44112
44115
  /**
44113
44116
  * A conversation summary.
@@ -44941,6 +44944,25 @@ declare class ResearchClient {
44941
44944
  * ```
44942
44945
  */
44943
44946
  runToCompletion(sessionId: string): Promise<ResearchSessionResponse>;
44947
+ /**
44948
+ * Resume an interrupted or failed research session.
44949
+ *
44950
+ * A session left in a non-`Completed` state — e.g. swept to `Failed` after a
44951
+ * server restart killed its in-process pipeline — is otherwise stuck. Resuming
44952
+ * re-runs the pipeline, continuing from the session's persisted partial
44953
+ * progress (papers ingested, findings, cycles), and can reach `Completed`.
44954
+ * Like {@link runToCompletion} the run is long-lived server-side; the UI
44955
+ * typically calls this fire-and-forget and polls {@link getSession}.
44956
+ *
44957
+ * @param sessionId - The session ID (UUID) to resume.
44958
+ * @throws {ApiError} 409 if the session is already `Completed`, 404 if unknown.
44959
+ *
44960
+ * @example
44961
+ * ```ts
44962
+ * await client.research.resumeSession('session-uuid');
44963
+ * ```
44964
+ */
44965
+ resumeSession(sessionId: string): Promise<ResearchSessionResponse>;
44944
44966
  /**
44945
44967
  * Delete a research session and all associated data.
44946
44968
  *
package/dist/index.d.ts CHANGED
@@ -109,7 +109,7 @@ type JsonValue$1 = string | number | boolean | null | JsonValue$1[] | object;
109
109
  * This is the single source of truth for the version constant.
110
110
  * The `scripts/release.sh` script updates this value alongside `package.json`.
111
111
  */
112
- declare const SDK_VERSION = "1.11.0";
112
+ declare const SDK_VERSION = "1.12.1";
113
113
  /**
114
114
  * Authentication mode for the SDK.
115
115
  *
@@ -44108,6 +44108,9 @@ interface TurnDto {
44108
44108
  osfql?: string | null;
44109
44109
  /** Per-claim provenance annotations (assistant turns only). */
44110
44110
  claimAnnotations?: ClaimAnnotationDto[] | null;
44111
+ /** MATCH result rows (assistant turns only), persisted by the backend so a
44112
+ * "show me a table of X" answer keeps its table across a reload. */
44113
+ queryResults?: Record<string, OsfqlValue>[] | null;
44111
44114
  }
44112
44115
  /**
44113
44116
  * A conversation summary.
@@ -44941,6 +44944,25 @@ declare class ResearchClient {
44941
44944
  * ```
44942
44945
  */
44943
44946
  runToCompletion(sessionId: string): Promise<ResearchSessionResponse>;
44947
+ /**
44948
+ * Resume an interrupted or failed research session.
44949
+ *
44950
+ * A session left in a non-`Completed` state — e.g. swept to `Failed` after a
44951
+ * server restart killed its in-process pipeline — is otherwise stuck. Resuming
44952
+ * re-runs the pipeline, continuing from the session's persisted partial
44953
+ * progress (papers ingested, findings, cycles), and can reach `Completed`.
44954
+ * Like {@link runToCompletion} the run is long-lived server-side; the UI
44955
+ * typically calls this fire-and-forget and polls {@link getSession}.
44956
+ *
44957
+ * @param sessionId - The session ID (UUID) to resume.
44958
+ * @throws {ApiError} 409 if the session is already `Completed`, 404 if unknown.
44959
+ *
44960
+ * @example
44961
+ * ```ts
44962
+ * await client.research.resumeSession('session-uuid');
44963
+ * ```
44964
+ */
44965
+ resumeSession(sessionId: string): Promise<ResearchSessionResponse>;
44944
44966
  /**
44945
44967
  * Delete a research session and all associated data.
44946
44968
  *
package/dist/index.js CHANGED
@@ -5,7 +5,7 @@ var __export = (target, all) => {
5
5
  };
6
6
 
7
7
  // src/config.ts
8
- var SDK_VERSION = "1.11.0";
8
+ var SDK_VERSION = "1.12.1";
9
9
  function resolveConfig(config) {
10
10
  if (!config.baseUrl) {
11
11
  throw new Error("ClientConfig.baseUrl is required");
@@ -22616,7 +22616,11 @@ function TurnDtoFromApiToFront(dto) {
22616
22616
  // Generated contract types this as `any[]` — the wire shape is ClaimAnnotationDto.
22617
22617
  claimAnnotations: dto.claim_annotations?.map(
22618
22618
  ClaimAnnotationDtoFromApiToFront
22619
- )
22619
+ ),
22620
+ // `query_results` isn't on the (stale) generated TurnDto contract yet, but the
22621
+ // backend now persists & returns it on assistant turns. Pass the rows straight
22622
+ // through like the message-response mapper does, so a reloaded turn keeps its table.
22623
+ queryResults: dto.query_results ?? void 0
22620
22624
  };
22621
22625
  }
22622
22626
  function ConversationSummaryDtoFromApiToFront(dto) {
@@ -23295,6 +23299,33 @@ var ResearchClient = class {
23295
23299
  });
23296
23300
  return ResearchSessionResponseFromApiToFront(response.data);
23297
23301
  }
23302
+ /**
23303
+ * Resume an interrupted or failed research session.
23304
+ *
23305
+ * A session left in a non-`Completed` state — e.g. swept to `Failed` after a
23306
+ * server restart killed its in-process pipeline — is otherwise stuck. Resuming
23307
+ * re-runs the pipeline, continuing from the session's persisted partial
23308
+ * progress (papers ingested, findings, cycles), and can reach `Completed`.
23309
+ * Like {@link runToCompletion} the run is long-lived server-side; the UI
23310
+ * typically calls this fire-and-forget and polls {@link getSession}.
23311
+ *
23312
+ * @param sessionId - The session ID (UUID) to resume.
23313
+ * @throws {ApiError} 409 if the session is already `Completed`, 404 if unknown.
23314
+ *
23315
+ * @example
23316
+ * ```ts
23317
+ * await client.research.resumeSession('session-uuid');
23318
+ * ```
23319
+ */
23320
+ async resumeSession(sessionId) {
23321
+ const response = await this.http.request({
23322
+ path: `/api/v1/research/sessions/${encodeURIComponent(sessionId)}/resume`,
23323
+ method: "POST",
23324
+ secure: true,
23325
+ format: "json"
23326
+ });
23327
+ return ResearchSessionResponseFromApiToFront(response.data);
23328
+ }
23298
23329
  /**
23299
23330
  * Delete a research session and all associated data.
23300
23331
  *