@alien_intelligence/data-api-client 1.22.0 → 2.1.0

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.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/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.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/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.22.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -62,7 +62,7 @@ export interface DatasetsApiInterface {
      */
     createDatasetApiV1DatasetsPost(requestParameters: CreateDatasetApiV1DatasetsPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Dataset>;
     /**
-     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with MinIO files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in MinIO, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
+     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with S3 files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in object storage, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
      * @summary Delete Dataset
      * @param {number} datasetId
      * @param {boolean} [force] Force deletion even if entries are in error status (may leave orphaned resources)
@@ -72,7 +72,7 @@ export interface DatasetsApiInterface {
      */
     deleteDatasetApiV1DatasetsDatasetIdDeleteRaw(requestParameters: DeleteDatasetApiV1DatasetsDatasetIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
-     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with MinIO files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in MinIO, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
+     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with S3 files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in object storage, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
      * Delete Dataset
      */
     deleteDatasetApiV1DatasetsDatasetIdDelete(requestParameters: DeleteDatasetApiV1DatasetsDatasetIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
@@ -180,12 +180,12 @@ export declare class DatasetsApi extends runtime.BaseAPI implements DatasetsApiI
      */
     createDatasetApiV1DatasetsPost(requestParameters: CreateDatasetApiV1DatasetsPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Dataset>;
     /**
-     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with MinIO files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in MinIO, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
+     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with S3 files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in object storage, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
      * Delete Dataset
      */
     deleteDatasetApiV1DatasetsDatasetIdDeleteRaw(requestParameters: DeleteDatasetApiV1DatasetsDatasetIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
-     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with MinIO files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in MinIO, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
+     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with S3 files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in object storage, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
      * Delete Dataset
      */
     deleteDatasetApiV1DatasetsDatasetIdDelete(requestParameters: DeleteDatasetApiV1DatasetsDatasetIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;

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.22.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -82,7 +82,7 @@ class DatasetsApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with MinIO files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in MinIO, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
+     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with S3 files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in object storage, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
      * Delete Dataset
      */
     async deleteDatasetApiV1DatasetsDatasetIdDeleteRaw(requestParameters, initOverrides) {
@@ -103,7 +103,7 @@ class DatasetsApi extends runtime.BaseAPI {
         return new runtime.VoidApiResponse(response);
     }
     /**
-     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with MinIO files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in MinIO, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
+     * Delete dataset and all related resources (entries, weights, files).  This performs a cascading deletion: 1. Deletes all weights (with S3 files) 2. Deletes all entries (with S3 files, Qdrant vectors, Meilisearch docs) 3. Each entry triggers its own deletion webhook 4. Each weight triggers its own deletion webhook 5. Finally deletes the dataset itself  If any errors occur during cascade, the dataset is NOT deleted and a detailed error report is returned (unless force=True).  **Force Mode**: When force=True, entries in \"error\" status will be deleted from the database even if external cleanup fails. This may leave orphaned resources in object storage, Qdrant, or Meilisearch. Use only for cleaning up stuck datasets.  Args:     dataset_id: Dataset ID to delete     force: Force deletion of entries in error status (default: False)     request: FastAPI request     repo: Dataset repository     cascade_service: Cascade deletion service  Raises:     HTTPException 404: Dataset not found     HTTPException 409: Cascade deletion failed (with error details, unless force=True)     HTTPException 503: Object storage refused access, or the cascade exceeded its         time budget. The dataset is kept in both cases; repeating the request resumes.
      * Delete Dataset
      */
     async deleteDatasetApiV1DatasetsDatasetIdDelete(requestParameters, initOverrides) {

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.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/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.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/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.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/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.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/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.22.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -128,7 +128,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.
@@ -139,7 +139,7 @@ export interface EntriesApiInterface {
         [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<{
@@ -194,7 +194,7 @@ export interface EntriesApiInterface {
         [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.
@@ -203,7 +203,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>;
@@ -294,7 +294,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
@@ -304,7 +304,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>;
@@ -338,7 +338,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
@@ -349,7 +349,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>;
@@ -389,14 +389,14 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     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.
      * Delete Entry
      */
     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<{
@@ -437,12 +437,12 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
         [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.
      * Get Ingest Contract Usage
      */
     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>;
@@ -505,12 +505,12 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     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.
      * Save Processed Content
      */
     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>;
@@ -535,12 +535,12 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     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.
      * Upload File To Entry
      */
     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>;

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.22.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -138,7 +138,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * 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, initOverrides) {
@@ -156,7 +156,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response);
     }
     /**
-     * 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, initOverrides) {
@@ -253,7 +253,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * 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, initOverrides) {
@@ -271,7 +271,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.IngestContractUsageResponseFromJSON)(jsonValue));
     }
     /**
-     * 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 = {}, initOverrides) {
@@ -445,7 +445,7 @@ class EntriesApi extends runtime.BaseAPI {
         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 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, initOverrides) {
@@ -468,7 +468,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.SaveProcessedContentResponseFromJSON)(jsonValue));
     }
     /**
-     * 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, initOverrides) {
@@ -538,7 +538,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * 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, initOverrides) {
@@ -581,7 +581,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.UploadFileResponseFromJSON)(jsonValue));
     }
     /**
-     * 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, 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.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/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.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/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.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/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.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/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.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/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.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/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.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/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.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/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.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/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.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/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.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/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.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/dist/src/models/AdmissionLaneHealth.d.ts

@@ -2,7 +2,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/dist/src/models/AdmissionLaneHealth.js

@@ -5,7 +5,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/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.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/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.22.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).