chore(sdk): update vendored OpenAPI spec and regenerate client

packages/sdk/src/generated/base.ts

@@ -4,7 +4,7 @@
  * Aignostics Platform API
  *  The Aignostics Platform is a cloud-based service that enables organizations to access advanced computational pathology applications through a secure API.  The platform provides standardized access to Aignostics\' portfolio of computational pathology solutions, with Atlas H&E-TME serving as an example of the available API endpoints.   To begin using the platform, your organization must first be registered by our business support team. If you don\'t have an account yet, please contact your account manager or email support@aignostics.com to get started.   More information about our applications can be found on [https://platform.aignostics.com](https://platform.aignostics.com).  **How to authorize and test API endpoints:**  1. Click the \"Authorize\" button in the right corner below 3. Click \"Authorize\" button in the dialog to log in with your Aignostics Platform credentials 4. After successful login, you\'ll be redirected back and can use \"Try it out\" on any endpoint  **Note**: You only need to authorize once per session. The lock icons next to endpoints will show green when authorized.  
  *
- * The version of the OpenAPI document: 1.7.0
+ * The version of the OpenAPI document: 1.7.1
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

packages/sdk/src/generated/common.ts

@@ -4,7 +4,7 @@
  * Aignostics Platform API
  *  The Aignostics Platform is a cloud-based service that enables organizations to access advanced computational pathology applications through a secure API.  The platform provides standardized access to Aignostics\' portfolio of computational pathology solutions, with Atlas H&E-TME serving as an example of the available API endpoints.   To begin using the platform, your organization must first be registered by our business support team. If you don\'t have an account yet, please contact your account manager or email support@aignostics.com to get started.   More information about our applications can be found on [https://platform.aignostics.com](https://platform.aignostics.com).  **How to authorize and test API endpoints:**  1. Click the \"Authorize\" button in the right corner below 3. Click \"Authorize\" button in the dialog to log in with your Aignostics Platform credentials 4. After successful login, you\'ll be redirected back and can use \"Try it out\" on any endpoint  **Note**: You only need to authorize once per session. The lock icons next to endpoints will show green when authorized.  
  *
- * The version of the OpenAPI document: 1.7.0
+ * The version of the OpenAPI document: 1.7.1
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

packages/sdk/src/generated/configuration.ts

@@ -4,7 +4,7 @@
  * Aignostics Platform API
  *  The Aignostics Platform is a cloud-based service that enables organizations to access advanced computational pathology applications through a secure API.  The platform provides standardized access to Aignostics\' portfolio of computational pathology solutions, with Atlas H&E-TME serving as an example of the available API endpoints.   To begin using the platform, your organization must first be registered by our business support team. If you don\'t have an account yet, please contact your account manager or email support@aignostics.com to get started.   More information about our applications can be found on [https://platform.aignostics.com](https://platform.aignostics.com).  **How to authorize and test API endpoints:**  1. Click the \"Authorize\" button in the right corner below 3. Click \"Authorize\" button in the dialog to log in with your Aignostics Platform credentials 4. After successful login, you\'ll be redirected back and can use \"Try it out\" on any endpoint  **Note**: You only need to authorize once per session. The lock icons next to endpoints will show green when authorized.  
  *
- * The version of the OpenAPI document: 1.7.0
+ * The version of the OpenAPI document: 1.7.1
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

packages/sdk/src/generated/docs/InputArtifactCreationRequest.md

@@ -6,9 +6,9 @@ Input artifact containing the slide image and associated metadata.
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**name** | **string** | Type of artifact. For Atlas H&E-TME, use \"input_slide\" | [default to undefined]
+**name** | **string** | Name of the input artifact, as declared by the application version. The valid names for a version are the `input_artifacts[].name` values returned by `GET /v1/applications/{application_id}/versions/{version}`. For Atlas H&E-TME this is `\"whole_slide_image\"`. | [default to undefined]
 **download_url** | **string** | [Signed URL](https://cloud.google.com/cdn/docs/using-signed-urls) to the input artifact file. The URL should be valid for at least 6 days from the payload submission time. | [default to undefined]
-**metadata** | **{ [key: string]: any; }** | The metadata of the artifact, required by the application version. The JSON schema of the metadata can be requested by `/v1/versions/{application_version_id}`. The schema is located in `input_artifacts.[].metadata_schema` | [default to undefined]
+**metadata** | **{ [key: string]: any; }** | The metadata of the artifact, as required by the application version. The authoritative JSON schema is `input_artifacts[].metadata_schema` from `GET /v1/applications/{application_id}/versions/{version}`; it rejects unknown properties. The example shown is an Atlas H&E-TME snapshot and may lag behind the version you are running — always validate against the schema endpoint. | [default to undefined]
 
 ## Example
 

packages/sdk/src/generated/docs/PublicApi.md

@@ -201,7 +201,7 @@ const { status, data } = await apiInstance.createGrantV1AccessGrantsPost(
 # **createRunV1RunsPost**
 > RunCreationResponse createRunV1RunsPost(runCreationRequest)
 
-This endpoint initiates a processing run for a selected application and version, and returns a `run_id` for tracking purposes.  Slide processing occurs asynchronously, allowing you to retrieve results for individual slides as soon as they complete processing. The system typically processes slides in batches. Below is an example of the required payload for initiating an Atlas H&E TME processing run.   ### Payload  The payload includes `application_id`, optional `version_number`, and `items` base fields.  `application_id` is the unique identifier for the application. `version_number` is the semantic version to use. If not provided, the latest available version will be used.  `items` includes the list of the items to process (slides, in case of HETA application). Every item has a set of standard fields defined by the API, plus the custom_metadata, specific to the chosen application.  Example payload structure with the comments: ``` {     application_id: \"he-tme\",     version_number: \"1.0.0-beta\",     items: [{         \"external_id\": \"slide_1\",         \"custom_metadata\": {\"project\": \"sample-study\"},         \"input_artifacts\": [{             \"name\": \"user_slide\",             \"download_url\": \"https://...\",             \"metadata\": {                 \"specimen\": {                   \"disease\": \"LUNG_CANCER\",                   \"tissue\": \"LUNG\"                 },                 \"staining_method\": \"H&E\",                 \"width_px\": 136223,                 \"height_px\": 87761,                 \"resolution_mpp\": 0.2628238,                 \"media-type\":\"image/tiff\",                 \"checksum_base64_crc32c\": \"64RKKA==\"             }         }]     }] } ```  | Parameter  | Description | | :---- | :---- | | `application_id` required | Unique ID for the application | | `version_number` optional | Semantic version of the application. If not provided, the latest available version will be used | | `items` required | List of submitted items i.e. whole slide images (WSIs) with parameters described below. | | `external_id` required | Unique WSI name or ID for easy reference to items, provided by the caller. The `external_id` should be unique across all items of the run.  | | `input_artifacts` required | List of provided artifacts for a WSI; at the moment Atlas H&E-TME receives only 1 artifact per slide (the slide itself), but for some other applications this can be a slide and a segmentation map  | | `name` required | Type of artifact; Atlas H&E-TME supports only `\"input_slide\"` | | `download_url` required | Signed URL to the input file in the S3 or GCS; Should be valid for at least 6 days | | `specimen: disease` required | Supported cancer types for Atlas H&E-TME (see full list in Atlas H&E-TME manual) | | `specimen: tissue` required | Supported tissue types for Atlas H&E-TME (see full list in Atlas H&E-TME manual) | | `staining_method` required | WSI stain bio-marker; Atlas H&E-TME supports only `\"H&E\"` | | `width_px` required | Integer value. Number of pixels of the WSI in the X dimension. | | `height_px` required | Integer value. Number of pixels of the WSI in the Y dimension. | | `resolution_mpp` required | Resolution of WSI in micrometers per pixel; check allowed range in Atlas H&E-TME manual | | `media-type` required | Supported media formats; available values are: image/tiff  (for .tiff or .tif WSI), application/dicom (for DICOM ), application/zip (for zipped DICOM), and application/octet-stream  (for .svs WSI) | | `checksum_base64_crc32c` required | Base64-encoded big-endian CRC32C checksum of the WSI image |    ### Response  The endpoint returns the run UUID. After that, the job is scheduled for the execution in the background.  To check the status of the run, call `GET v1/runs/{run_id}` endpoint with the returned run UUID.  ### Rejection  Apart from the authentication, authorization, and malformed input error, the request can be rejected when specific quota limit is exceeded. More details on quotas is described in the documentation
+This endpoint initiates a processing run for a selected application and version, and returns a `run_id` for tracking purposes.  Item processing occurs asynchronously, allowing you to retrieve results for individual items as soon as they complete processing. The system typically processes items in batches.  ### Payload  The payload includes `application_id`, optional `version_number`, and `items` base fields.  `application_id` is the unique identifier for the application. `version_number` is the semantic version to use. If not provided, the latest version available to you will be used.  `items` includes the list of the items to process (slides, in case of the Atlas H&E-TME application). Every item has a set of standard fields defined by the API, plus `input_artifacts[].metadata`, whose shape is defined by the chosen application version.  Below is an example payload for initiating an Atlas H&E-TME (`he-tme`) run:  ```json {   \"application_id\": \"he-tme\",   \"items\": [     {       \"external_id\": \"slide_1\",       \"custom_metadata\": {         \"case\": \"abc\"       },       \"input_artifacts\": [         {           \"name\": \"whole_slide_image\",           \"download_url\": \"https://example-bucket.s3.amazonaws.com/slide1.tiff?signature=...\",           \"metadata\": {             \"checksum_base64_crc32c\": \"64RKKA==\",             \"staining_method\": \"H&E\",             \"specimen\": {               \"disease\": \"LUNG_CANCER\",               \"tissue\": \"LUNG\"             },             \"media_type\": \"image/tiff\",             \"width_px\": 136223,             \"height_px\": 87761,             \"resolution_mpp\": 0.2628238           }         }       ]     }   ] } ```  > **The example above is a snapshot, not a contract.** Applications are released independently of > this API, so the `input_artifacts[].metadata` shape shown here may lag behind the version you are > running. The authoritative schema for a version is always `input_artifacts[].metadata_schema` > from `GET /v1/applications/{application_id}/versions/{version}`. That schema rejects unknown > properties, so a stale field name will fail validation with `400`.  | Parameter | Description | | :---- | :---- | | `application_id` **required** | Unique ID for the application | | `version_number` optional | Semantic version of the application. If not provided, the latest version available to you will be used | | `items` **required** | List of submitted items, i.e. whole slide images (WSIs), with the parameters described below | | `external_id` **required** | Unique WSI name or ID for easy reference to items, provided by the caller. Must be unique across all items of the run | | `custom_metadata` optional | Free-form JSON stored verbatim alongside the run or item. Not processed or validated by the platform, and not application-specific | | `input_artifacts` **required** | List of provided artifacts for a WSI. Atlas H&E-TME receives 1 artifact per slide (the slide itself); other applications may take more, e.g. a slide plus a segmentation map | | `name` **required** | Name of the artifact as declared by the application version. Atlas H&E-TME accepts only `\"whole_slide_image\"` | | `download_url` **required** | Signed URL to the input file in S3 or GCS. Should be valid for at least 6 days |  The remaining fields below live inside `input_artifacts[].metadata` and are governed by the application version\'s `metadata_schema`. The following applies to Atlas H&E-TME:  | Metadata field | Description | | :---- | :---- | | `checksum_base64_crc32c` **required** | Base64-encoded big-endian CRC32C checksum of the WSI image | | `staining_method` **required** | WSI stain bio-marker; Atlas H&E-TME supports only `\"H&E\"` | | `specimen.disease` **required** | One of `BREAST_CANCER`, `LUNG_CANCER`, `COLORECTAL_CANCER`, `BLADDER_CANCER`, `LIVER_CANCER`, `PROSTATE_CANCER`, `PANCREATIC_CANCER`, `STOMACH_CANCER`, `OVARIAN_CANCER`, or `OTHER` | | `specimen.tissue` optional | Tissue of origin. Allowed values depend on `disease`; defaults to `OTHER` when omitted | | `media_type` optional | Media format of the WSI: `image/tiff` (.tiff/.tif), `application/dicom` (DICOM), `application/zip` (zipped DICOM), or `application/octet-stream` (.svs) | | `resolution_mpp` optional | Resolution of the WSI in micrometers per pixel | | `width_px` optional | Number of pixels of the WSI in the X dimension | | `height_px` optional | Number of pixels of the WSI in the Y dimension |  ### Response  The endpoint returns the run UUID. After that, the job is scheduled for execution in the background.  To check the status of the run, call `GET /v1/runs/{run_id}` with the returned run UUID.  ### Rejection  Beyond authentication, authorization, and malformed-input errors, the request is rejected with `402 Payment Required` when a quota limit would be exceeded. See the quota documentation for details.
 
 ### Example
 
@@ -247,9 +247,10 @@ const { status, data } = await apiInstance.createRunV1RunsPost(
 | Status code | Description | Response headers |
 |-------------|-------------|------------------|
 |**201** | Successful Response |  -  |
-|**404** | Application version not found |  -  |
-|**403** | Forbidden - You don\'t have permission to create this run |  -  |
+|**404** | Application or application version not found |  -  |
 |**400** | Bad Request - Input validation failed |  -  |
+|**402** | Payment Required - A quota limit (slides per run, or monthly slides) would be exceeded by this run |  -  |
+|**403** | Forbidden - You don\'t have permission to create this run |  -  |
 |**422** | Validation Error |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
@@ -310,7 +311,7 @@ const { status, data } = await apiInstance.createShareTokenV1AccessShareTokensPo
 # **deleteRunItemsV1RunsRunIdArtifactsDelete**
 > any deleteRunItemsV1RunsRunIdArtifactsDelete()
 
-This endpoint allows the caller to explicitly delete artifacts generated by a run. It can only be invoked when the run has reached a final state, i.e. `PROCESSED`, `CANCELED_SYSTEM`, or `CANCELED_USER`. Note that by default, all artifacts are automatically deleted 30 days after the run finishes, regardless of whether the caller explicitly requests such deletion.
+This endpoint allows the caller to explicitly delete artifacts generated by a run.  It can only be invoked once the run has reached state `TERMINATED` (as reported by `GET /v1/runs/{run_id}`); calling it earlier returns `409`.  Note that by default, all artifacts are automatically deleted 30 days after the run finishes, regardless of whether the caller explicitly requests such deletion.
 
 ### Example
 
@@ -356,6 +357,9 @@ const { status, data } = await apiInstance.deleteRunItemsV1RunsRunIdArtifactsDel
 |-------------|-------------|------------------|
 |**200** | Run artifacts deleted |  -  |
 |**404** | Run not found |  -  |
+|**403** | Forbidden - You don\'t have permission to delete this run\'s artifacts |  -  |
+|**409** | Conflict - The run has not terminated yet |  -  |
+|**410** | Gone - Run artifacts have already been deleted |  -  |
 |**422** | Validation Error |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)

packages/sdk/src/generated/index.ts

@@ -4,7 +4,7 @@
  * Aignostics Platform API
  *  The Aignostics Platform is a cloud-based service that enables organizations to access advanced computational pathology applications through a secure API.  The platform provides standardized access to Aignostics\' portfolio of computational pathology solutions, with Atlas H&E-TME serving as an example of the available API endpoints.   To begin using the platform, your organization must first be registered by our business support team. If you don\'t have an account yet, please contact your account manager or email support@aignostics.com to get started.   More information about our applications can be found on [https://platform.aignostics.com](https://platform.aignostics.com).  **How to authorize and test API endpoints:**  1. Click the \"Authorize\" button in the right corner below 3. Click \"Authorize\" button in the dialog to log in with your Aignostics Platform credentials 4. After successful login, you\'ll be redirected back and can use \"Try it out\" on any endpoint  **Note**: You only need to authorize once per session. The lock icons next to endpoints will show green when authorized.  
  *
- * The version of the OpenAPI document: 1.7.0
+ * The version of the OpenAPI document: 1.7.1
  * 
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).