@alien_intelligence/data-api-client 1.16.6 → 1.18.7

package/dist/src/apis/AdminApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/AdminApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DatasetsApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DatasetsApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DefaultApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DefaultApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/EmbeddingsApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,12 +10,12 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { EmbeddingResponse, GenerateEmbeddingsRequest, HealthResponse, ModelInfo } from '../models/index';
+import type { EmbeddingProvider, EmbeddingResponse, GenerateEmbeddingsRequest, HealthResponse, ModelInfo } from '../models/index';
 export interface GenerateEmbeddingsApiV1EmbeddingsGeneratePostRequest {
     generateEmbeddingsRequest: GenerateEmbeddingsRequest;
 }
 export interface ListModelsApiV1EmbeddingsModelsGetRequest {
-    provider?: string | null;
+    provider?: EmbeddingProvider | null;
 }
 /**
  * EmbeddingsApi - interface
@@ -54,7 +54,7 @@ export interface EmbeddingsApiInterface {
     /**
      * Get available embedding models for each provider
      * @summary List available models
-     * @param {string} [provider]
+     * @param {EmbeddingProvider} [provider]
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof EmbeddingsApiInterface

package/dist/src/apis/EmbeddingsApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/EntriesApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -10,7 +10,7 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { BatchContentRequest, BatchContentResponse, BatchGetEntriesRequest, BatchGetEntriesResponse, Entry, EntryCreateRequest, EntryCreateResponse, EntryUpdateRequest, IngestContractUsageResponse, MoveEntryRequest, MoveEntryResponse, SaveProcessedContentRequest, SaveProcessedContentResponse, UploadFileResponse } from '../models/index';
+import type { BatchContentRequest, BatchContentResponse, BatchGetEntriesRequest, BatchGetEntriesResponse, Entry, EntryCreateRequest, EntryCreateResponse, EntryUpdateRequest, IngestContractUsageResponse, MoveEntryRequest, MoveEntryResponse, ProcessingResetResponse, SaveProcessedContentRequest, SaveProcessedContentResponse, UploadFileResponse } from '../models/index';
 export interface BatchGetContentApiV1EntriesBatchContentPostRequest {
     batchContentRequest: BatchContentRequest;
 }
@@ -56,6 +56,9 @@ export interface MoveEntryApiV1EntriesEntryIdMovePostRequest {
     entryId: number;
     moveEntryRequest: MoveEntryRequest;
 }
+export interface ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest {
+    entryId: number;
+}
 export interface SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest {
     entryId: number;
     saveProcessedContentRequest: SaveProcessedContentRequest;
@@ -216,7 +219,7 @@ export interface EntriesApiInterface {
      */
     getWorkflowStatusApiV1EntriesEntryIdWorkflowStatusGet(requestParameters: GetWorkflowStatusApiV1EntriesEntryIdWorkflowStatusGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<any>;
     /**
-     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
+     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  A chunk is identified by its entry and its chunk_index. Posting an index again replaces that chunk\'s point, including a point an earlier data-api version stored for it under a random id. Indices the request does not name are kept, so an entry\'s chunks may be sent over several requests, with chunk_index counted across all of them. Points past the last index of a shorter re-run are kept too: reset the entry first (`POST /entries/{entry_id}/processing/reset`) when re-sending all of its chunks.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
      * @summary Index Entry Chunks
      * @param {number} entryId
      * @param {{ [key: string]: any; }} requestBody
@@ -228,7 +231,7 @@ export interface EntriesApiInterface {
         [key: string]: any;
     }>>;
     /**
-     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
+     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  A chunk is identified by its entry and its chunk_index. Posting an index again replaces that chunk\'s point, including a point an earlier data-api version stored for it under a random id. Indices the request does not name are kept, so an entry\'s chunks may be sent over several requests, with chunk_index counted across all of them. Points past the last index of a shorter re-run are kept too: reset the entry first (`POST /entries/{entry_id}/processing/reset`) when re-sending all of its chunks.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
      * Index Entry Chunks
      */
     indexEntryChunksApiV1EntriesEntryIdChunksPost(requestParameters: IndexEntryChunksApiV1EntriesEntryIdChunksPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{
@@ -270,6 +273,20 @@ export interface EntriesApiInterface {
      * Move Entry
      */
     moveEntryApiV1EntriesEntryIdMovePost(requestParameters: MoveEntryApiV1EntriesEntryIdMovePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<MoveEntryResponse>;
+    /**
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, its segment documents, its entries-index document, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * @summary Reset Entry Processing
+     * @param {number} entryId
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof EntriesApiInterface
+     */
+    resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ProcessingResetResponse>>;
+    /**
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, its segment documents, its entries-index document, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Reset Entry Processing
+     */
+    resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ProcessingResetResponse>;
     /**
      * Save processed content for an entry.  Called by workers/pipelines after processing.  Safe to repeat. The whole `processed` section is rewritten, so a re-run replaces the previous segmentation instead of merging with it - a second pass that yields fewer segments leaves none of the first pass\'s behind. That matters beyond tidiness: the backend reaper and this cluster\'s own staleness detection can both fire for the same entry, and re-ingest being idempotent is what makes double-triggering harmless.
      * @summary Save Processed Content
@@ -286,7 +303,7 @@ export interface EntriesApiInterface {
      */
     saveProcessedContentApiV1EntriesEntryIdProcessedPost(requestParameters: SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SaveProcessedContentResponse>;
     /**
-     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
+     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 409: The tenant is processed by the platform (PROCESSING_ENGINE=workers, acknowledged   by the platform). The dataset\'s pipeline_config is kept, unused, so switching back   to argo restores this - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
      * @summary Trigger Pipeline
      * @param {number} entryId
      * @param {*} [options] Override http request option.
@@ -295,7 +312,7 @@ export interface EntriesApiInterface {
      */
     triggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRaw(requestParameters: TriggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<any>>;
     /**
-     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
+     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 409: The tenant is processed by the platform (PROCESSING_ENGINE=workers, acknowledged   by the platform). The dataset\'s pipeline_config is kept, unused, so switching back   to argo restores this - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
      * Trigger Pipeline
      */
     triggerPipelineApiV1EntriesEntryIdTriggerPipelinePost(requestParameters: TriggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<any>;
@@ -434,14 +451,14 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     getWorkflowStatusApiV1EntriesEntryIdWorkflowStatusGet(requestParameters: GetWorkflowStatusApiV1EntriesEntryIdWorkflowStatusGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<any>;
     /**
-     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
+     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  A chunk is identified by its entry and its chunk_index. Posting an index again replaces that chunk\'s point, including a point an earlier data-api version stored for it under a random id. Indices the request does not name are kept, so an entry\'s chunks may be sent over several requests, with chunk_index counted across all of them. Points past the last index of a shorter re-run are kept too: reset the entry first (`POST /entries/{entry_id}/processing/reset`) when re-sending all of its chunks.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
      * Index Entry Chunks
      */
     indexEntryChunksApiV1EntriesEntryIdChunksPostRaw(requestParameters: IndexEntryChunksApiV1EntriesEntryIdChunksPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<{
         [key: string]: any;
     }>>;
     /**
-     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
+     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  A chunk is identified by its entry and its chunk_index. Posting an index again replaces that chunk\'s point, including a point an earlier data-api version stored for it under a random id. Indices the request does not name are kept, so an entry\'s chunks may be sent over several requests, with chunk_index counted across all of them. Points past the last index of a shorter re-run are kept too: reset the entry first (`POST /entries/{entry_id}/processing/reset`) when re-sending all of its chunks.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
      * Index Entry Chunks
      */
     indexEntryChunksApiV1EntriesEntryIdChunksPost(requestParameters: IndexEntryChunksApiV1EntriesEntryIdChunksPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{
@@ -471,6 +488,16 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      * Move Entry
      */
     moveEntryApiV1EntriesEntryIdMovePost(requestParameters: MoveEntryApiV1EntriesEntryIdMovePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<MoveEntryResponse>;
+    /**
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, its segment documents, its entries-index document, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Reset Entry Processing
+     */
+    resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ProcessingResetResponse>>;
+    /**
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, its segment documents, its entries-index document, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Reset Entry Processing
+     */
+    resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ProcessingResetResponse>;
     /**
      * Save processed content for an entry.  Called by workers/pipelines after processing.  Safe to repeat. The whole `processed` section is rewritten, so a re-run replaces the previous segmentation instead of merging with it - a second pass that yields fewer segments leaves none of the first pass\'s behind. That matters beyond tidiness: the backend reaper and this cluster\'s own staleness detection can both fire for the same entry, and re-ingest being idempotent is what makes double-triggering harmless.
      * Save Processed Content
@@ -482,12 +509,12 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     saveProcessedContentApiV1EntriesEntryIdProcessedPost(requestParameters: SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SaveProcessedContentResponse>;
     /**
-     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
+     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 409: The tenant is processed by the platform (PROCESSING_ENGINE=workers, acknowledged   by the platform). The dataset\'s pipeline_config is kept, unused, so switching back   to argo restores this - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
      * Trigger Pipeline
      */
     triggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRaw(requestParameters: TriggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<any>>;
     /**
-     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
+     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 409: The tenant is processed by the platform (PROCESSING_ENGINE=workers, acknowledged   by the platform). The dataset\'s pipeline_config is kept, unused, so switching back   to argo restores this - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
      * Trigger Pipeline
      */
     triggerPipelineApiV1EntriesEntryIdTriggerPipelinePost(requestParameters: TriggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<any>;

package/dist/src/apis/EntriesApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -310,7 +310,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
+     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  A chunk is identified by its entry and its chunk_index. Posting an index again replaces that chunk\'s point, including a point an earlier data-api version stored for it under a random id. Indices the request does not name are kept, so an entry\'s chunks may be sent over several requests, with chunk_index counted across all of them. Points past the last index of a shorter re-run are kept too: reset the entry first (`POST /entries/{entry_id}/processing/reset`) when re-sending all of its chunks.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
      * Index Entry Chunks
      */
     async indexEntryChunksApiV1EntriesEntryIdChunksPostRaw(requestParameters, initOverrides) {
@@ -333,7 +333,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response);
     }
     /**
-     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
+     * Index chunks for an entry into Qdrant vector database.  This endpoint is called by processing pipelines after chunking and embedding.  A chunk is identified by its entry and its chunk_index. Posting an index again replaces that chunk\'s point, including a point an earlier data-api version stored for it under a random id. Indices the request does not name are kept, so an entry\'s chunks may be sent over several requests, with chunk_index counted across all of them. Points past the last index of a shorter re-run are kept too: reset the entry first (`POST /entries/{entry_id}/processing/reset`) when re-sending all of its chunks.  Request body: {     \"chunks\": [         {             \"chunk_text\": \"...\",             \"chunk_index\": 0,             \"embedding\": [0.1, 0.2, ...],             \"metadata\": {\"page_number\": 1, ...}         }     ] }  Note: Collection name is always determined by the tenant\'s QDRANT_COLLECTION_NAME configuration.
      * Index Entry Chunks
      */
     async indexEntryChunksApiV1EntriesEntryIdChunksPost(requestParameters, initOverrides) {
@@ -409,6 +409,32 @@ class EntriesApi extends runtime.BaseAPI {
         const response = await this.moveEntryApiV1EntriesEntryIdMovePostRaw(requestParameters, initOverrides);
         return await response.value();
     }
+    /**
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, its segment documents, its entries-index document, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Reset Entry Processing
+     */
+    async resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters, initOverrides) {
+        if (requestParameters['entryId'] == null) {
+            throw new runtime.RequiredError('entryId', 'Required parameter "entryId" was null or undefined when calling resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost().');
+        }
+        const queryParameters = {};
+        const headerParameters = {};
+        const response = await this.request({
+            path: `/api/v1/entries/{entry_id}/processing/reset`.replace(`{${"entry_id"}}`, encodeURIComponent(String(requestParameters['entryId']))),
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+        return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.ProcessingResetResponseFromJSON)(jsonValue));
+    }
+    /**
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, its segment documents, its entries-index document, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Reset Entry Processing
+     */
+    async resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost(requestParameters, initOverrides) {
+        const response = await this.resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters, initOverrides);
+        return await response.value();
+    }
     /**
      * Save processed content for an entry.  Called by workers/pipelines after processing.  Safe to repeat. The whole `processed` section is rewritten, so a re-run replaces the previous segmentation instead of merging with it - a second pass that yields fewer segments leaves none of the first pass\'s behind. That matters beyond tidiness: the backend reaper and this cluster\'s own staleness detection can both fire for the same entry, and re-ingest being idempotent is what makes double-triggering harmless.
      * Save Processed Content
@@ -441,7 +467,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
+     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 409: The tenant is processed by the platform (PROCESSING_ENGINE=workers, acknowledged   by the platform). The dataset\'s pipeline_config is kept, unused, so switching back   to argo restores this - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
      * Trigger Pipeline
      */
     async triggerPipelineApiV1EntriesEntryIdTriggerPipelinePostRaw(requestParameters, initOverrides) {
@@ -464,7 +490,7 @@ class EntriesApi extends runtime.BaseAPI {
         }
     }
     /**
-     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
+     * Trigger pipeline workflow for an entry.  This endpoint: 1. Validates entry exists and is in a triggerable state 2. Validates dataset has a pipeline configured and enabled 3. Builds Argo Workflow from pipeline config using PipelineBuilder 4. Updates entry status to \'processing\' 5. Submits workflow to Argo Workflows 6. Returns workflow metadata  **Valid Entry Statuses**: uploaded, error **Requirements**: Dataset must have pipeline_config with enabled=true  **Error Responses**: - 404: Entry not found - 409: The tenant is processed by the platform (PROCESSING_ENGINE=workers, acknowledged   by the platform). The dataset\'s pipeline_config is kept, unused, so switching back   to argo restores this - 400: Invalid entry status, pipeline not configured, or pipeline disabled - 500: Workflow submission failed
      * Trigger Pipeline
      */
     async triggerPipelineApiV1EntriesEntryIdTriggerPipelinePost(requestParameters, initOverrides) {

package/dist/src/apis/HealthApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/HealthApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/PipelinesApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/PipelinesApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SearchApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SearchApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SyncApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SyncApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WebhooksApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WebhooksApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WeightsApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WeightsApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ArtifactInputConfig.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ArtifactInputConfig.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentRequest.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentRequest.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesRequest.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesRequest.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResult.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResult.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.16.6
+ * The version of the OpenAPI document: 1.18.7
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).