@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.cjs +33 -2
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +23 -1
- package/dist/index.d.ts +23 -1
- package/dist/index.js +33 -2
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/dist/index.cjs
CHANGED
|
@@ -7,7 +7,7 @@ var __export = (target, all) => {
|
|
|
7
7
|
};
|
|
8
8
|
|
|
9
9
|
// src/config.ts
|
|
10
|
-
var SDK_VERSION = "1.
|
|
10
|
+
var SDK_VERSION = "1.12.1";
|
|
11
11
|
function resolveConfig(config) {
|
|
12
12
|
if (!config.baseUrl) {
|
|
13
13
|
throw new Error("ClientConfig.baseUrl is required");
|
|
@@ -22618,7 +22618,11 @@ function TurnDtoFromApiToFront(dto) {
|
|
|
22618
22618
|
// Generated contract types this as `any[]` — the wire shape is ClaimAnnotationDto.
|
|
22619
22619
|
claimAnnotations: dto.claim_annotations?.map(
|
|
22620
22620
|
ClaimAnnotationDtoFromApiToFront
|
|
22621
|
-
)
|
|
22621
|
+
),
|
|
22622
|
+
// `query_results` isn't on the (stale) generated TurnDto contract yet, but the
|
|
22623
|
+
// backend now persists & returns it on assistant turns. Pass the rows straight
|
|
22624
|
+
// through like the message-response mapper does, so a reloaded turn keeps its table.
|
|
22625
|
+
queryResults: dto.query_results ?? void 0
|
|
22622
22626
|
};
|
|
22623
22627
|
}
|
|
22624
22628
|
function ConversationSummaryDtoFromApiToFront(dto) {
|
|
@@ -23297,6 +23301,33 @@ var ResearchClient = class {
|
|
|
23297
23301
|
});
|
|
23298
23302
|
return ResearchSessionResponseFromApiToFront(response.data);
|
|
23299
23303
|
}
|
|
23304
|
+
/**
|
|
23305
|
+
* Resume an interrupted or failed research session.
|
|
23306
|
+
*
|
|
23307
|
+
* A session left in a non-`Completed` state — e.g. swept to `Failed` after a
|
|
23308
|
+
* server restart killed its in-process pipeline — is otherwise stuck. Resuming
|
|
23309
|
+
* re-runs the pipeline, continuing from the session's persisted partial
|
|
23310
|
+
* progress (papers ingested, findings, cycles), and can reach `Completed`.
|
|
23311
|
+
* Like {@link runToCompletion} the run is long-lived server-side; the UI
|
|
23312
|
+
* typically calls this fire-and-forget and polls {@link getSession}.
|
|
23313
|
+
*
|
|
23314
|
+
* @param sessionId - The session ID (UUID) to resume.
|
|
23315
|
+
* @throws {ApiError} 409 if the session is already `Completed`, 404 if unknown.
|
|
23316
|
+
*
|
|
23317
|
+
* @example
|
|
23318
|
+
* ```ts
|
|
23319
|
+
* await client.research.resumeSession('session-uuid');
|
|
23320
|
+
* ```
|
|
23321
|
+
*/
|
|
23322
|
+
async resumeSession(sessionId) {
|
|
23323
|
+
const response = await this.http.request({
|
|
23324
|
+
path: `/api/v1/research/sessions/${encodeURIComponent(sessionId)}/resume`,
|
|
23325
|
+
method: "POST",
|
|
23326
|
+
secure: true,
|
|
23327
|
+
format: "json"
|
|
23328
|
+
});
|
|
23329
|
+
return ResearchSessionResponseFromApiToFront(response.data);
|
|
23330
|
+
}
|
|
23300
23331
|
/**
|
|
23301
23332
|
* Delete a research session and all associated data.
|
|
23302
23333
|
*
|