@alien_intelligence/data-api-client 1.22.0 → 2.1.0

package/src/src/apis/DefaultApi.ts

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

package/src/src/apis/EmbeddingsApi.ts

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

package/src/src/apis/EntriesApi.ts

@@ -4,7 +4,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.22.0
+ * The version of the OpenAPI document: 2.1.0
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -208,7 +208,7 @@ export interface EntriesApiInterface {
     createEntryApiV1EntriesPost(requestParameters: CreateEntryApiV1EntriesPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<EntryCreateResponse>;
 
     /**
-     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"minio\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         },         \"warnings\": [\"component1\", \"component2\"] (optional, if any cleanups failed)     }
+     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"storage\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         }     }  Raises:     HTTPException 409: A blocking cleanup failed; the entry is kept with status         \"error\". The detail carries the same cleanup_status and failed_components,         the blocking components that failed (\"database\", \"storage\", \"qdrant\").     HTTPException 404: Entry not found.     HTTPException 503: Object storage refused access; the entry is untouched.
      * @summary Delete Entry
      * @param {number} entryId 
      * @param {*} [options] Override http request option.
@@ -218,7 +218,7 @@ export interface EntriesApiInterface {
     deleteEntryApiV1EntriesEntryIdDeleteRaw(requestParameters: DeleteEntryApiV1EntriesEntryIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<{ [key: string]: any; }>>;
 
     /**
-     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"minio\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         },         \"warnings\": [\"component1\", \"component2\"] (optional, if any cleanups failed)     }
+     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"storage\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         }     }  Raises:     HTTPException 409: A blocking cleanup failed; the entry is kept with status         \"error\". The detail carries the same cleanup_status and failed_components,         the blocking components that failed (\"database\", \"storage\", \"qdrant\").     HTTPException 404: Entry not found.     HTTPException 503: Object storage refused access; the entry is untouched.
      * Delete Entry
      */
     deleteEntryApiV1EntriesEntryIdDelete(requestParameters: DeleteEntryApiV1EntriesEntryIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{ [key: string]: any; }>;
@@ -274,7 +274,7 @@ export interface EntriesApiInterface {
     getEntryContentApiV1EntriesEntryIdContentGet(requestParameters: GetEntryContentApiV1EntriesEntryIdContentGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{ [key: string]: any; }>;
 
     /**
-     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
+     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  Counts are written in batches, by each pod every `ingest_usage_flush_interval_s` (`IngestContractUsageTally`), so posts from the last interval may not be counted yet, and a pod killed without a graceful stop loses at most one interval of its own. Either can only lower a count or move `last_seen_at` earlier by that much.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
      * @summary Get Ingest Contract Usage
      * @param {number} [datasetId] 
      * @param {*} [options] Override http request option.
@@ -284,7 +284,7 @@ export interface EntriesApiInterface {
     getIngestContractUsageApiV1EntriesIngestContractUsageGetRaw(requestParameters: GetIngestContractUsageApiV1EntriesIngestContractUsageGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<IngestContractUsageResponse>>;
 
     /**
-     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
+     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  Counts are written in batches, by each pod every `ingest_usage_flush_interval_s` (`IngestContractUsageTally`), so posts from the last interval may not be counted yet, and a pod killed without a graceful stop loses at most one interval of its own. Either can only lower a count or move `last_seen_at` earlier by that much.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
      * Get Ingest Contract Usage
      */
     getIngestContractUsageApiV1EntriesIngestContractUsageGet(requestParameters: GetIngestContractUsageApiV1EntriesIngestContractUsageGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<IngestContractUsageResponse>;
@@ -378,7 +378,7 @@ export interface EntriesApiInterface {
     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 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.  Holds a database connection only while it reads or writes the database. The tenant database sits behind PgBouncer in transaction mode, where an open transaction owns one of the tenant\'s few server connections; this route used to keep one open from its first read to after the response, across the object-storage write and the Meilisearch indexing - on 2026-10-28 a bulk ingest kept ~39 of them idle in transaction at once, for seconds each. It now runs as three short transactions with the external calls between them: read the entry, store the objects, write the row and commit, index, record what the index holds. `_commit_processed_row` and `_index_processed_entry` say how each stays consistent with what was done while no lock was held.
      * @summary Save Processed Content
      * @param {number} entryId 
      * @param {SaveProcessedContentRequest} saveProcessedContentRequest 
@@ -389,7 +389,7 @@ export interface EntriesApiInterface {
     saveProcessedContentApiV1EntriesEntryIdProcessedPostRaw(requestParameters: SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SaveProcessedContentResponse>>;
 
     /**
-     * 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 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.  Holds a database connection only while it reads or writes the database. The tenant database sits behind PgBouncer in transaction mode, where an open transaction owns one of the tenant\'s few server connections; this route used to keep one open from its first read to after the response, across the object-storage write and the Meilisearch indexing - on 2026-10-28 a bulk ingest kept ~39 of them idle in transaction at once, for seconds each. It now runs as three short transactions with the external calls between them: read the entry, store the objects, write the row and commit, index, record what the index holds. `_commit_processed_row` and `_index_processed_entry` say how each stays consistent with what was done while no lock was held.
      * Save Processed Content
      */
     saveProcessedContentApiV1EntriesEntryIdProcessedPost(requestParameters: SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SaveProcessedContentResponse>;
@@ -428,7 +428,7 @@ export interface EntriesApiInterface {
     updateEntryApiV1EntriesEntryIdPatch(requestParameters: UpdateEntryApiV1EntriesEntryIdPatchRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Entry>;
 
     /**
-     * Upload a file to an existing entry.  This saves the file to MinIO and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
+     * Upload a file to an existing entry.  This saves the file to object storage and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
      * @summary Upload File To Entry
      * @param {number} entryId 
      * @param {Blob} file File to upload
@@ -440,7 +440,7 @@ export interface EntriesApiInterface {
     uploadFileToEntryApiV1EntriesEntryIdUploadPostRaw(requestParameters: UploadFileToEntryApiV1EntriesEntryIdUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<UploadFileResponse>>;
 
     /**
-     * Upload a file to an existing entry.  This saves the file to MinIO and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
+     * Upload a file to an existing entry.  This saves the file to object storage and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
      * Upload File To Entry
      */
     uploadFileToEntryApiV1EntriesEntryIdUploadPost(requestParameters: UploadFileToEntryApiV1EntriesEntryIdUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<UploadFileResponse>;
@@ -567,7 +567,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"minio\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         },         \"warnings\": [\"component1\", \"component2\"] (optional, if any cleanups failed)     }
+     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"storage\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         }     }  Raises:     HTTPException 409: A blocking cleanup failed; the entry is kept with status         \"error\". The detail carries the same cleanup_status and failed_components,         the blocking components that failed (\"database\", \"storage\", \"qdrant\").     HTTPException 404: Entry not found.     HTTPException 503: Object storage refused access; the entry is untouched.
      * Delete Entry
      */
     async deleteEntryApiV1EntriesEntryIdDeleteRaw(requestParameters: DeleteEntryApiV1EntriesEntryIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<{ [key: string]: any; }>> {
@@ -593,7 +593,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"minio\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         },         \"warnings\": [\"component1\", \"component2\"] (optional, if any cleanups failed)     }
+     * Delete entry and all its files.  Warning: This permanently deletes all files from storage. Also deletes associated chunks from Qdrant if they exist.  Returns:     Dict with deletion status:     {         \"message\": \"Entry deleted successfully\",         \"cleanup_status\": {             \"database\": bool,             \"webhook\": bool,             \"storage\": bool,             \"qdrant\": bool,             \"meilisearch\": bool         }     }  Raises:     HTTPException 409: A blocking cleanup failed; the entry is kept with status         \"error\". The detail carries the same cleanup_status and failed_components,         the blocking components that failed (\"database\", \"storage\", \"qdrant\").     HTTPException 404: Entry not found.     HTTPException 503: Object storage refused access; the entry is untouched.
      * Delete Entry
      */
     async deleteEntryApiV1EntriesEntryIdDelete(requestParameters: DeleteEntryApiV1EntriesEntryIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{ [key: string]: any; }> {
@@ -719,7 +719,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
+     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  Counts are written in batches, by each pod every `ingest_usage_flush_interval_s` (`IngestContractUsageTally`), so posts from the last interval may not be counted yet, and a pod killed without a graceful stop loses at most one interval of its own. Either can only lower a count or move `last_seen_at` earlier by that much.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
      * Get Ingest Contract Usage
      */
     async getIngestContractUsageApiV1EntriesIngestContractUsageGetRaw(requestParameters: GetIngestContractUsageApiV1EntriesIngestContractUsageGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<IngestContractUsageResponse>> {
@@ -742,7 +742,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
+     * Report which ingest shapes this cluster\'s producers actually post.  Declared before `/{entry_id}` so the literal path wins the match.  This exists to date a decision. The legacy `{\"text\": ...}` shape is still accepted and its boundaries derived, and it will stop being accepted at some point; picking that point without counting means either breaking a live producer or waiting indefinitely. LDS, BnF, TI and bioRxiv/medRxiv all write here.  Counts are written in batches, by each pod every `ingest_usage_flush_interval_s` (`IngestContractUsageTally`), so posts from the last interval may not be counted yet, and a pod killed without a graceful stop loses at most one interval of its own. Either can only lower a count or move `last_seen_at` earlier by that much.  No `x-organization-id` scope, deliberately and consistently with every other route on this router: one data-cluster serves one tenant, and `Dataset` carries no organization column to filter on (see its docstring - organizations live in the backend catalogue, not here). Omitting `dataset_id` therefore spans this tenant\'s own datasets and nobody else\'s, which is the same reach `GET /entries` already has.  Args:     dataset_id: Restrict to a single dataset, or omit for every dataset.  Returns:     The tenant this cluster serves and one row per dataset and shape.
      * Get Ingest Contract Usage
      */
     async getIngestContractUsageApiV1EntriesIngestContractUsageGet(requestParameters: GetIngestContractUsageApiV1EntriesIngestContractUsageGetRequest = {}, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<IngestContractUsageResponse> {
@@ -978,7 +978,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * 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 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.  Holds a database connection only while it reads or writes the database. The tenant database sits behind PgBouncer in transaction mode, where an open transaction owns one of the tenant\'s few server connections; this route used to keep one open from its first read to after the response, across the object-storage write and the Meilisearch indexing - on 2026-10-28 a bulk ingest kept ~39 of them idle in transaction at once, for seconds each. It now runs as three short transactions with the external calls between them: read the entry, store the objects, write the row and commit, index, record what the index holds. `_commit_processed_row` and `_index_processed_entry` say how each stays consistent with what was done while no lock was held.
      * Save Processed Content
      */
     async saveProcessedContentApiV1EntriesEntryIdProcessedPostRaw(requestParameters: SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<SaveProcessedContentResponse>> {
@@ -1014,7 +1014,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * 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 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.  Holds a database connection only while it reads or writes the database. The tenant database sits behind PgBouncer in transaction mode, where an open transaction owns one of the tenant\'s few server connections; this route used to keep one open from its first read to after the response, across the object-storage write and the Meilisearch indexing - on 2026-10-28 a bulk ingest kept ~39 of them idle in transaction at once, for seconds each. It now runs as three short transactions with the external calls between them: read the entry, store the objects, write the row and commit, index, record what the index holds. `_commit_processed_row` and `_index_processed_entry` say how each stays consistent with what was done while no lock was held.
      * Save Processed Content
      */
     async saveProcessedContentApiV1EntriesEntryIdProcessedPost(requestParameters: SaveProcessedContentApiV1EntriesEntryIdProcessedPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<SaveProcessedContentResponse> {
@@ -1107,7 +1107,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * Upload a file to an existing entry.  This saves the file to MinIO and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
+     * Upload a file to an existing entry.  This saves the file to object storage and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
      * Upload File To Entry
      */
     async uploadFileToEntryApiV1EntriesEntryIdUploadPostRaw(requestParameters: UploadFileToEntryApiV1EntriesEntryIdUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<UploadFileResponse>> {
@@ -1165,7 +1165,7 @@ export class EntriesApi extends runtime.BaseAPI implements EntriesApiInterface {
     }
 
     /**
-     * Upload a file to an existing entry.  This saves the file to MinIO and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
+     * Upload a file to an existing entry.  This saves the file to object storage and updates the entry manifest in the appropriate section.  **File Types**: - `original`: Original uploaded files (default) - stored in manifest.original.files - `processing`: Intermediate processing artifacts - stored in manifest.processing.files - `processed`: Final processed outputs - stored in manifest.processed.additional_files  Can be called multiple times to upload additional files of any type.
      * Upload File To Entry
      */
     async uploadFileToEntryApiV1EntriesEntryIdUploadPost(requestParameters: UploadFileToEntryApiV1EntriesEntryIdUploadPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<UploadFileResponse> {

package/src/src/apis/HealthApi.ts

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

package/src/src/apis/PipelinesApi.ts

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

package/src/src/apis/SearchApi.ts

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

package/src/src/apis/SyncApi.ts

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

package/src/src/apis/WebhooksApi.ts

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

package/src/src/apis/WeightsApi.ts

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

package/src/src/models/AdmissionLaneHealth.ts

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

package/src/src/models/ArtifactInputConfig.ts

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

package/src/src/models/BatchContentRequest.ts

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

package/src/src/models/BatchContentResponse.ts

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

package/src/src/models/BatchGetEntriesRequest.ts

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

package/src/src/models/BatchGetEntriesResponse.ts

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

package/src/src/models/ChunkSearchResponse.ts

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

package/src/src/models/ChunkSearchResult.ts

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

package/src/src/models/CollectionInfo.ts

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

package/src/src/models/ComponentArtifact.ts

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

package/src/src/models/ComponentListResponse.ts

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

package/src/src/models/ComponentMetadata.ts

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

package/src/src/models/ComponentParameter.ts

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

package/src/src/models/Dataset.ts

@@ -4,7 +4,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.22.0
+ * The version of the OpenAPI document: 2.1.0
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -94,7 +94,7 @@ export interface Dataset {
      */
     currentSchemaVersion?: string;
     /**
-     * Base storage path in MinIO/S3 (e.g., 'datasets/123')
+     * Base storage path in object storage (e.g., 'datasets/123')
      * @type {string}
      * @memberof Dataset
      */

package/src/src/models/DatasetCreateRequest.ts

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

package/src/src/models/DatasetListResponse.ts

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

package/src/src/models/DatasetPipelineConfig.ts

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

package/src/src/models/DatasetResponse.ts

@@ -4,7 +4,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 1.22.0
+ * The version of the OpenAPI document: 2.1.0
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -89,7 +89,7 @@ export interface DatasetResponse {
      */
     currentSchemaVersion?: string;
     /**
-     * Base storage path in MinIO/S3 (e.g., 'datasets/123')
+     * Base storage path in object storage (e.g., 'datasets/123')
      * @type {string}
      * @memberof DatasetResponse
      */

package/src/src/models/DatasetSchemaDefinition.ts

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

package/src/src/models/DatasetSchemaDefinitionCreate.ts

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

package/src/src/models/DatasetSchemaOriginal.ts

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

package/src/src/models/DatasetSchemaProcessed.ts

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

package/src/src/models/DatasetSchemaProcessing.ts

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

package/src/src/models/DatasetType.ts

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

package/src/src/models/DatasetUpdateRequest.ts

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

package/src/src/models/DatasetUpdateSchemaRequest.ts

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

package/src/src/models/Default.ts

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

package/src/src/models/DeprecationNotice.ts

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

package/src/src/models/DerivedPageReport.ts

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

package/src/src/models/EmbeddingProvider.ts

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

package/src/src/models/EmbeddingPurpose.ts

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

package/src/src/models/EmbeddingResponse.ts

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