@keboola/api-client 36.0.0 → 40.0.0

package/dist/{storage-LYwFQPNO.js → storage-CZQHZcXG.js}

@@ -1,10 +1,10 @@
-import { a as poller, t as jobStatus } from "./jobStatus-PSZJMTiA.js";
-import { t as concurrent } from "./concurrent-CH9fbNr3.js";
-import { h as KeboolaHttpHeader, r as isApiError, s as HttpHeader } from "./createFetchClient-U-ZrwPl2.js";
-import { t as validateConnectionStatus } from "./validateConnectionStatus-olE2sQ3U.js";
-import { t as createGenericFetchClient } from "./createGenericFetchClient-rxvUUbap.js";
-import { t as createOpenapiFetchClient } from "./createOpenapiFetchClient-BVSc9ibR.js";
-import { t as createAuthHeaders } from "./auth-aItmDu45.js";
+import { a as poller, t as jobStatus } from "./jobStatus-CfRtsIpv.js";
+import { t as concurrent } from "./concurrent-BacWxPwi.js";
+import { g as ApiError, h as KeboolaHttpHeader, r as isApiError, s as HttpHeader } from "./createFetchClient-DXHQK63w.js";
+import { t as validateConnectionStatus } from "./validateConnectionStatus-BEGu8wXT.js";
+import { t as createGenericFetchClient } from "./createGenericFetchClient-Dg1rgzmG.js";
+import { t as createOpenapiFetchClient } from "./createOpenapiFetchClient-DZUOVupy.js";
+import { t as createAuthHeaders } from "./auth-DworfoPy.js";
 //#region src/utils/async/series.ts
 /**
 * Executes a callback function on an array of items in series (one at a time).
@@ -17,6 +17,28 @@ const series = async (options) => concurrent({
 	concurrency: 1
 });
 //#endregion
+//#region src/errors/readableReason.ts
+const isRecord = (value) => typeof value === "object" && value !== null && !Array.isArray(value);
+/**
+* Whether this error's `message` is a status line rather than a sentence.
+*
+* - Only the base `ApiError`: its subclasses carry reader-facing wording that must be kept.
+*/
+const carriesStatusLine = (error) => error.constructor === ApiError;
+/**
+* The part of a failure worth putting in front of a reader, or `undefined` when there is none.
+*
+* - A plain `ApiError`: the service's message from the body, never the status line.
+* - Any other error: its `message` as-is.
+* - `undefined` means render your own wording; don't test for an empty `message` instead.
+*/
+const readableReason = (error) => {
+	if (!(error instanceof Error)) return void 0;
+	if (!carriesStatusLine(error)) return error.message === "" ? void 0 : error.message;
+	const message = isRecord(error.data) ? error.data.message : void 0;
+	return typeof message === "string" && message !== "" ? message : void 0;
+};
+//#endregion
 //#region src/errors/ServiceUnavailableError.ts
 var ServiceUnavailableError = class ServiceUnavailableError extends Error {
 	constructor(serviceId, path, clientName) {
@@ -103,12 +125,11 @@ const createMergeRequests = (client) => {
 //#endregion
 //#region src/clients/storage/branches/branches.ts
 /**
-* The `/v2/storage/dev-branches` contract is spec-derived; three defects remain.
+* Dev-branches client; the spec has three defects.
 *
-* - `creatorToken` is a bare `object`, so `DevBranch` re-types it and the two reads are asserted.
-* - The create and delete answer `JobResponse` — flat, with `status: string` — where `Job<T>` is a
-*   discriminated union over `status`, so both jobs are asserted.
-* - Duplicate: the create is also declared on `/dev-branches/` (trailing slash); drop it.
+* - `creatorToken` is a bare `object`, so `DevBranch` re-types it and reads are asserted.
+* - Create and delete answer a flat `JobResponse`, not the `Job<T>` union, so jobs are asserted.
+* - The create is also declared on `/dev-branches/` (trailing slash); drop it.
 */
 const createBranches = (client, poller) => {
 	/**
@@ -119,8 +140,6 @@ const createBranches = (client, poller) => {
 		return data;
 	};
 	/**
-	* Creates a development branch. Async — returns a job to poll.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/dev-branches/POST/v2/storage/dev-branches
 	*/
 	const createDevBranchAsync = async (body) => {
@@ -128,16 +147,12 @@ const createBranches = (client, poller) => {
 		return data;
 	};
 	/**
-	* Creates a development branch and waits for the job to finish.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/dev-branches/POST/v2/storage/dev-branches
 	*/
 	const createDevBranchAndWait = async (body, options) => {
 		return poller(await createDevBranchAsync(body), options).start();
 	};
 	/**
-	* Renames a development branch or changes its description.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/dev-branches/PUT/v2/storage/dev-branches/{id}
 	*/
 	const updateDevBranch = async ({ id, name, description }) => {
@@ -151,8 +166,6 @@ const createBranches = (client, poller) => {
 		return data;
 	};
 	/**
-	* Deletes a development branch. Async — returns a job to poll.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/dev-branches/DELETE/v2/storage/dev-branches/{id}
 	*/
 	const deleteDevBranchAsync = async (id) => {
@@ -160,12 +173,9 @@ const createBranches = (client, poller) => {
 		return data;
 	};
 	/**
-	* Deletes a development branch and waits for the job to finish.
-	*
-	* - Resolves with how the wait ended, so nothing throws: `done` carries the finished
-	*   `devBranchDelete` job.
-	* - A job that ended as `error` is a `done` wait carrying a failed job — it finished. `timedOut`,
-	*   `exhausted`, `aborted` and `errored` are the endings with no job to read.
+	* - Never throws; resolves with how the wait ended.
+	* - `done` carries the finished job, even one that ended as `error`.
+	* - `timedOut`, `exhausted`, `aborted` and `errored` carry no job.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/dev-branches/DELETE/v2/storage/dev-branches/{id}
 	*/
@@ -173,8 +183,7 @@ const createBranches = (client, poller) => {
 		return poller(await deleteDevBranchAsync(id), options).start();
 	};
 	/**
-	* Returns every metadata record on a branch. The branch is the object here, so `branchId` is the
-	* thing being addressed rather than the branch a request is scoped to.
+	* `branchId` is the branch the metadata is on, not a request scope.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/metadata/GET/v2/storage/branch/{branchId}/metadata
 	*/
@@ -183,8 +192,6 @@ const createBranches = (client, poller) => {
 		return data;
 	};
 	/**
-	* Adds or updates metadata on a branch.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/metadata/POST/v2/storage/branch/{branchId}/metadata
 	*/
 	const saveDevBranchMetadata = async ({ branchId, metadata }, signal) => {
@@ -195,8 +202,6 @@ const createBranches = (client, poller) => {
 		return data;
 	};
 	/**
-	* Deletes a single metadata entry from a branch.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/metadata/DELETE/v2/storage/branch/{branchId}/metadata/{metadataId}
 	*/
 	const deleteDevBranchMetadata = async ({ branchId, metadataId }, signal) => {
@@ -220,31 +225,14 @@ const createBranches = (client, poller) => {
 //#endregion
 //#region src/clients/storage/bucketExternal/bucketExternal.ts
 /**
-* An external bucket wraps a schema that already exists in the project's backend (Snowflake or
-* BigQuery) rather than one Keboola created. Registering it is what makes the rest of this namespace
-* apply: only an external bucket needs its table metadata refreshed, manually or on a cron.
+* External buckets wrap a schema that already exists in the backend (Snowflake or BigQuery).
 *
-* Two spec mismatches recur and account for the assertions below:
-* - **jobs** — the spec's `JobResponse` is a flat shape with `status: string`, while `Job<T>` is a
-*   discriminated union over `status` carrying typed `results`. Every job return is asserted, whether
-*   the operation declares a `JobResponse` or no body at all.
-* - **`async` query** — `registerBucketAsync` is invoked with `async: true` but declares
-*   `query: never`.
-*
-* What the Storage spec needs, per operation:
-*
-* - `POST /buckets/register` (`BucketRegisterAction`)
-*   - query: `never` → really accepts `async`
-*   - response: contentless `default` → really a `bucketRegister` job
-* - `PUT /buckets/{bucketId}/refresh` (`BucketRefreshAction`)
-*   - response: 202 `JobResponse` → really a `bucketRefresh` job
-* `GET /buckets/register-guide` and the scheduled-task create are the operations whose spec is
-* already right — their bodies, queries and responses are generated, not asserted.
+* - Only they need table metadata refreshed, manually or on a cron.
+* - Job returns are asserted: the spec's flat `JobResponse` is not the `Job<T>` union.
+* - The `POST /buckets/register` spec lacks the `async` query and the `bucketRegister` job response.
 */
 const createBucketExternal = (client) => {
 	/**
-	* Registers an external bucket. Async — returns a job to poll.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/POST/v2/storage/buckets/register
 	*/
 	const registerBucketAsync = async (body, signal) => {
@@ -255,7 +243,7 @@ const createBucketExternal = (client) => {
 		return data;
 	};
 	/**
-	* Returns a markdown guide for registering an external bucket.
+	* Returns markdown.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/buckets/GET/v2/storage/buckets/register-guide
 	*/
@@ -267,8 +255,6 @@ const createBucketExternal = (client) => {
 		return data;
 	};
 	/**
-	* Refreshes an external bucket's table metadata. Async — returns a job to poll.
-	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/buckets/PUT/v2/storage/buckets/{bucketId}/refresh
 	*/
 	const refreshExternalBucketAsync = async ({ bucketId, ...query }, signal) => {
@@ -302,10 +288,7 @@ const createBucketExternal = (client) => {
 //#endregion
 //#region src/clients/storage/bucketListings/utils.ts
 /**
-* The two halves of the `bigquery.subscribers` wire format: a GCP IAM principal, which the Storage
-* spec documents as "prefixed with `user:` or `group:`". The write path uses `toBackendSubscribers`;
-* reads hand back the raw `string[]`, so a consumer that renders or edits subscribers decodes with
-* `fromBackendSubscribers` rather than re-deriving the prefix rule.
+* Encodes subscribers as GCP IAM principals (`user:`/`group:`); `fromBackendSubscribers` decodes.
 */
 const toBackendSubscribers = (subscribers) => subscribers.map((s) => `${s.type}:${s.email}`);
 const fromBackendSubscribers = (raw) => {
@@ -327,17 +310,9 @@ const fromBackendSubscribers = (raw) => {
 /**
 * Builds the PATCH body for a listing update.
 *
-* Every field is copied only when the caller actually supplied it, because `description` carries
-* three distinct meanings: absent means "leave it alone", `null` means "clear it", and a string
-* means "set it". Evaluating the coercion unconditionally would turn an omitted description into a
-* `null` and silently clear it.
-*
-* Throws when nothing was supplied: the backend answers an empty PATCH with a job that lands in
-* `success` without changing anything, so a caller would poll it and report a save that never
-* happened. Gate the call on the form's "dirty" state rather than relying on this.
-*
-* Do not "normalize" the `exposure*` names without coordinating with the bucket-listing backend
-* owner.
+* - Copies only supplied fields: `description` absent keeps it, `null` clears it, a string sets it.
+* - Throws when nothing was supplied: an empty PATCH yields a `success` job that changed nothing.
+* - Keep the `exposure*` names unless the bucket-listing backend owner agrees.
 */
 const toUpdateListingBody = (input) => {
 	const body = {};
@@ -350,26 +325,17 @@ const toUpdateListingBody = (input) => {
 //#endregion
 //#region src/clients/storage/bucketListings/bucketListings.ts
 /**
-* A bucket listing (exposure) publishes a bucket to a marketplace — BigQuery Analytics Hub is the
-* only backend today, which is why every write carries a `bigquery` key.
-*
-* What the Storage spec needs, per operation:
-*
-* - `POST` / `PATCH` / `DELETE /buckets/{bucketId}/listing`
-*   - response: 202 `JobResponse` → really `bucketListingCreate` / `bucketListingUpdate` /
-*     `bucketListingDelete` jobs. The spec's `JobResponse` is a flat shape with `status: string`,
-*     while `Job<T>` is a discriminated union over `status` carrying typed `results`, so each is
-*     asserted.
+* Bucket listings (exposures) publish a bucket to a marketplace.
 *
-* `GET /buckets/{bucketId}/listing` and `GET /listings` are the operations whose specs are already
-* right — their query and response types are generated, not asserted.
+* - BigQuery Analytics Hub is the only backend, hence the `bigquery` key on every write.
+* - Write jobs are asserted: the spec's flat `JobResponse` is not the `Job<T>` union.
 */
 const createBucketListings = (openApiClient) => {
 	/**
-	* Reads a bucket's listing, or `null` when the bucket has none (the endpoint 404s for both "no
-	* bucket" and "no listing"). The response is the spec shape: `bigquery` is optional there — it is
-	* present only for a BigQuery bucket, the only backend today — and `subscribers` inside it are the
-	* raw `user:`/`group:`-prefixed principals, which `fromBackendSubscribers` decodes.
+	* Returns `null` on 404: no bucket or no listing.
+	*
+	* - `bigquery` is present only for a BigQuery bucket.
+	* - Its `subscribers` are raw `user:`/`group:` principals; decode with `fromBackendSubscribers`.
 	*/
 	const getListing = async (bucketId, signal) => {
 		try {
@@ -395,11 +361,7 @@ const createBucketListings = (openApiClient) => {
 		return data;
 	};
 	/**
-	* Update a bucket exposure. At least one of `name`, `description`, or
-	* `subscribers` must be provided — the SDK throws synchronously if all three
-	* are absent, since the backend would otherwise no-op a PATCH with an empty
-	* body and we'd return a job that's already in `success` with no actual
-	* change. Callers should gate the call against the form's "dirty" state.
+	* Rejects when `name`, `description` and `subscribers` are all absent; gate on the form's dirty state.
 	*/
 	const updateListingAsync = async ({ bucketId, ...input }, signal) => {
 		const { data } = await openApiClient.patch("/v2/storage/buckets/{bucketId}/listing", {
@@ -428,29 +390,11 @@ const createBucketListings = (openApiClient) => {
 //#endregion
 //#region src/clients/storage/buckets/buckets.ts
 /**
-* Everything here runs through the OpenAPI client except `updateBucket`, which cannot: the spec
-* declares no `put` on `/v2/storage/buckets/{bucketId}` (nor on the branch variant), so the operation
-* is missing outright rather than mistyped. That one keeps the generic client, which is why this
-* factory still takes both.
-*
-* One mismatch recurs: the spec's `JobResponse` is a flat shape with `status: string`, while `Job<T>`
-* is a discriminated union over `status` carrying typed `results`, so every job return is asserted.
-*
-* What the Storage spec needs, per operation:
-*
-* - `PUT /buckets/{bucketId}` — **operation missing entirely**; really takes `UpdateBucketBody`
-*   (`displayName` / `description` / `color`) and answers a bucket detail
-* - `GET /branch/{branchId}/buckets` (`BucketsListAction`)
-*   - query: `include` is a `string` → really a repeatable list, sent comma-joined
-*   - response: `BucketCreateResponse[]` → really `Bucket[]` (a listing row, not a create result)
-* - `POST /buckets` (`BucketCreateAction`)
-*   - response: 201 `BucketCreateResponse` → really a bucket detail
-* - `DELETE /buckets/{bucketId}` (`BucketDeleteAction`)
-*   - response: 204 wins over the 202 `JobResponse` in success-code precedence, so the async variant's
-*     job is asserted
-* - `POST /buckets/{bucketId}/owner` (`BucketOwnerUpdateAction`)
-*   - body: `BucketOwnerUpdateRequest` is stubbed → really `{ email } | { id }`
-* */
+* Spec mismatches behind the assertions below:
+* - Job returns: the spec's flat `JobResponse` vs the `Job<T>` union; on delete, 204 shadows the 202.
+* - List/create responses are really `Bucket[]` / a bucket detail; list `include` is comma-joined.
+* - Owner-update body is stubbed; really `{ email } | { id }`.
+*/
 const createBuckets = (openApiClient, client) => {
 	const getBuckets = async ({ branchId, ...query }, signal) => {
 		const { data } = await openApiClient.get("/v2/storage/branch/{branchId}/buckets", {
@@ -492,8 +436,8 @@ const createBuckets = (openApiClient, client) => {
 	/**
 	* Deletes a bucket synchronously.
 	*
-	* Refused outright on the stacks we test against (`400 storage.buckets.syncDeleteDisabled`,
-	* "Synchronous drop is not supported, use async call") — prefer `deleteBucketAsync` below.
+	* - Refused on the stacks we test against (`400 storage.buckets.syncDeleteDisabled`); prefer
+	*   `deleteBucketAsync`.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/buckets/DELETE/v2/storage/buckets/{bucketId}
 	*/
@@ -501,10 +445,7 @@ const createBuckets = (openApiClient, client) => {
 		await openApiClient.delete("/v2/storage/buckets/{bucketId}", { path: { bucketId: id } });
 	};
 	/**
-	* Deletes a bucket asynchronously and returns a job to poll.
-	* Required on GCP stacks where synchronous bucket deletion is not supported.
-	*
-	* `force` deletes all tables inside the bucket before removing it.
+	* Deletes a bucket asynchronously and returns a job to poll. Required on GCP stacks.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/buckets/DELETE/v2/storage/buckets/{bucketId}
 	*/
@@ -521,9 +462,8 @@ const createBuckets = (openApiClient, client) => {
 	/**
 	* Returns the owner of a bucket in the given branch.
 	*
-	* A bucket has no owner until one is assigned — reading it on a fresh bucket answers
-	* `404 storage.bucket.ownerNotFound`, so call `updateBucketOwner` first (or handle the 404 as
-	* "unassigned" rather than as a missing bucket).
+	* - A bucket without an assigned owner answers `404 storage.bucket.ownerNotFound`, not a missing
+	*   bucket.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/buckets/GET/v2/storage/branch/{branchId}/buckets/{bucketId}/owner
 	*/
@@ -588,36 +528,11 @@ const createBuckets = (openApiClient, client) => {
 //#endregion
 //#region src/clients/storage/bucketSharing/bucketSharing.ts
 /**
-* Two spec mismatches recur here and account for every assertion below:
-* - **jobs** — the spec's `JobResponse` is a flat shape with `status: string`, while `Job<T>` is a
-*   discriminated union over `status` carrying typed `results`. Every job return is asserted, whether
-*   the operation declares a `JobResponse` or no body at all.
-* - **`async` query** — all six share/unshare operations are invoked with `async: true` but declare
-*   `query: never`.
-*
-* What the Storage spec needs, per operation:
-*
-* - `POST /branch/{branchId}/buckets/{bucketId}/share-organization` / `-organization-project`
-*   - query: `never` → really accepts `async`
-*   - response: `BucketShareOrganizationResponse` / `…ProjectResponse` → really share jobs
-* - `POST /branch/{branchId}/buckets/{bucketId}/share-to-projects` / `-to-users`
-*   - query: `never` → really accepts `async`
-*   - body: `CreateBucketSharingToProjectsRequest` / `…ToUsersRequest` are stubbed
-*     (`Record<string, never>`) → really `{ targetProjectIds }` / `{ targetUsers }`
-*   - response: contentless `default` → really `bucketShareToProjects` / `bucketShareToAdmins` jobs
-* - `DELETE /branch/{branchId}/buckets/{bucketId}/share` (`BucketShareDeleteAction`)
-*   - query: `never` → really accepts `async`
-*   - response: `BucketShareDeleteResponse` → really a `bucketRemoveShare` job
-* - `DELETE /branch/{branchId}/buckets/{bucketId}/links/{linkedProjectId}` (`BucketForceUnlinkAction`)
-*   - query: `never` → really accepts `async`
-*   - path: `linkedProjectId` is a `number` → really a string
-*   - response: 202 `JobResponse` → really a `bucketForceUnlink` job
-* - `POST /buckets` (`BucketCreateAction`) — the link half of a create-or-link endpoint
-*   - response: the 201 "created or linked synchronously" wins over the 202 in success-code
-*     precedence, so the async variant's `bucketLink` job is asserted
-* - `GET /shared-buckets` (`SharedBucketsListAction`)
-*   - response: `Record<string, never>[]` → really a shared-bucket listing. This one is *not*
-*     asserted, so `SharedBuckets` is currently an empty-object array and callers get nothing useful.
+* Spec mismatches behind the assertions below:
+* - Job returns: the spec's flat `JobResponse` (or no body) vs the `Job<T>` union.
+* - Share/unshare declare `query: never`, but accept `async`.
+* - Share-to-projects/users bodies are stubbed; force-unlink `linkedProjectId` is really a string.
+* - `sharedBuckets` is not asserted, so it returns the spec's `Record<string, never>[]`.
 */
 const createBucketSharing = (openApiClient) => {
 	/**
@@ -749,24 +664,10 @@ const createBucketSharing = (openApiClient) => {
 //#endregion
 //#region src/clients/storage/columns/columns.ts
 /**
-* Every job return below is asserted in: the spec's `JobResponse` is a flat shape with
-* `status: string`, while `Job<T>` is a discriminated union over `status` carrying typed `results`.
-* That mismatch applies to both operations that declare a `JobResponse` and those that declare no
-* response body at all. What the Storage spec needs, per operation:
-*
-* - `POST /branch/{branchId}/tables/{id}/columns` (`ColumnCreateAction`)
-*   - body: none of `ColumnCreateRequest` / `SnowflakeAddColumnToTableRequest` /
-*     `BigqueryAddColumnToTableRequest` declares `basetype`, and they type `definition.length` as a
-*     `number` → really a string (a decimal length is sent as `'38,0'`)
-*   - response: 202 is contentless → really a `tableColumnAdd` job
-* - `DELETE /branch/{branchId}/tables/{tableId}/columns/{columnName}` (`ColumnDeleteAction`)
-*   - response: 202 declares `JobResponse` → really a `tableColumnDelete` job
-* - `POST /branch/{branchId}/tables/{tableId}/primary-key` (`PrimaryKeyCreateAction`)
-*   - body: `CreatePrimaryKeyRequest.skipDuplicatesCheck` is required → really optional (it has a
-*     documented `@default false`, so a caller omitting it is valid)
-*   - response: 202 is contentless → really a `tablePrimaryKeyAdd` job
-* - `DELETE /branch/{branchId}/tables/{tableId}/primary-key` (`PrimaryKeyDeleteAction`)
-*   - response: 202 declares `JobResponse` → really a `tablePrimaryKeyDelete` job
+* Spec mismatches behind the assertions below:
+* - Job returns: the spec's flat `JobResponse` (or no body) vs the `Job<T>` union.
+* - Add-column body lacks `basetype`; `definition.length` is really a string (`'38,0'`).
+* - Primary-key `skipDuplicatesCheck` is really optional (defaults to `false`).
 */
 const createColumns = (client) => {
 	/**
@@ -1032,17 +933,12 @@ const createConfigurationRows = (client) => {
 //#endregion
 //#region src/clients/storage/configurations/utils.ts
 /**
-* `expectedVersion` is the `version` field of the configuration the caller read, sent back as the
-* `If-Match` header so the write is conditional on nothing having changed since. What Storage does
-* with it:
+* Sends `expectedVersion` as `If-Match`. Storage answers:
 *
-* 1. Header omitted (`{}`) — no precondition, the write applies whatever the current version is.
-*    `purgeConfiguration` is the exception and answers 428, which is why its `expectedVersion` is
-*    required rather than optional.
-* 2. Version still current — the write applies.
-* 3. Version moved on since it was read — 412, and nothing is written.
-* 4. Value unusable — 400. Storage wants a strong entity tag, so the quotes are part of the value;
-*    a bare number, a weak validator or a tag list are all rejected.
+* 1. Omitted — no precondition (except `purgeConfiguration`: 428).
+* 2. Current — the write applies.
+* 3. Moved on — 412, nothing written.
+* 4. Not a strong quoted entity tag — 400.
 */
 const createVersionPrecondition = (expectedVersion) => expectedVersion === void 0 ? {} : { [HttpHeader.IF_MATCH]: `"${expectedVersion}"` };
 /**
@@ -1061,10 +957,8 @@ const parseSyncJobId = (headers) => {
 /**
 * Every configuration read is bridged to `ComponentConfig<T>` with `as unknown as`.
 *
-* - `BaseComponentConfig` re-tightens four fields the spec marks nullable and re-types the two
-*   free-form JSON ones, so the generated shape and the target never fully overlap.
-* - `ComponentConfig<T>` is a conditional over an unresolved `T`, which TypeScript will not check a
-*   direct conversion against either.
+* - `BaseComponentConfig` re-tightens and re-types spec fields, so the shapes never fully overlap.
+* - `ComponentConfig<T>` is a conditional over an unresolved `T`, which TS won't convert against.
 */
 const createConfigurations = (client) => {
 	const getConfiguration = async ({ componentId, configId, branchId }, signal) => {
@@ -1095,11 +989,10 @@ const createConfigurations = (client) => {
 		return data;
 	};
 	/**
-	* Resolve a merge conflict by deleting the configuration — the same rebase
-	* endpoint as `rebaseConfiguration`, but with an empty `diff` envelope. The
-	* dev-branch configuration is re-anchored onto the given default-branch
-	* `version` and its head version becomes a tombstone (soft delete). Returns
-	* the deleted configuration.
+	* Resolve a merge conflict by deleting the configuration.
+	*
+	* - Same rebase endpoint as `rebaseConfiguration`, with an empty `diff` envelope.
+	* - Re-anchors onto the default-branch `version`; the head version becomes a tombstone.
 	*/
 	const rebaseConfigurationToDeleted = async ({ branchId, componentId, configId, version }) => {
 		const { data } = await client.post("/v2/storage/branch/{branchId}/components/{componentId}/configs/{configurationId}/rebase", {
@@ -1126,14 +1019,10 @@ const createConfigurations = (client) => {
 		return data;
 	};
 	/**
-	* Updates an existing configuration. Only the fields provided are sent.
+	* Sends only the fields provided.
 	*
-	* - Resolves once the configuration is written.
-	* - Sending `workspaceId` also asks Storage to sync that workspace's output mapping against the
-	*   saved configuration. That part runs as a job: poll `syncJobId` through `jobs.getJob` when it
-	*   has to land before the caller reports success.
-	* - A `workspaceId` not linked to this component and configuration is rejected with 400, before
-	*   the configuration is written.
+	* - `workspaceId` also enqueues an output-mapping sync job; poll `syncJobId` via `jobs.getJob`.
+	* - A `workspaceId` not linked to this configuration is rejected with 400, before any write.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/component-configurations/PUT/v2/storage/branch/{branchId}/components/{componentId}/configs/{configurationId}
 	*/
@@ -1171,9 +1060,8 @@ const createConfigurations = (client) => {
 		return data;
 	};
 	/**
-	* Move a configuration to the trash — or, when it is in the trash already, purge it
-	* permanently. Pass `expectedVersion` to pin the version the delete was decided on;
-	* prefer `purgeConfiguration` when the permanent removal is the intent.
+	* Move a configuration to the trash — or purge it if it is already trashed.
+	* Prefer `purgeConfiguration` when permanent removal is the intent.
 	*/
 	const deleteConfiguration = async ({ branchId, componentId, configId, expectedVersion }) => {
 		await client.delete("/v2/storage/branch/{branchId}/components/{componentId}/configs/{configurationId}", { path: {
@@ -1184,9 +1072,9 @@ const createConfigurations = (client) => {
 	};
 	/**
 	* Permanently remove a trashed configuration, including its versions, rows and metadata.
-	* Unlike a second `deleteConfiguration`, this never falls back to a soft delete: purging a
-	* live configuration is rejected (400 `notInTrash`) rather than trashing it. Default branch
-	* only, and the token needs `canPurgeTrash`.
+	*
+	* - Purging a live configuration is rejected (400 `notInTrash`), never soft-deleted.
+	* - Default branch only; the token needs `canPurgeTrash`.
 	*/
 	const purgeConfiguration = async ({ branchId, componentId, configId, expectedVersion }) => {
 		await client.post("/v2/storage/branch/{branchId}/components/{componentId}/configs/{configurationId}/purge", { path: {
@@ -1196,13 +1084,10 @@ const createConfigurations = (client) => {
 		} }, { headers: { ...createVersionPrecondition(expectedVersion) } });
 	};
 	/**
-	* Purge configurations across components in one bounded fan-out. Like every `concurrent` caller
-	* it stops at the first rejection, and here that is a case to plan for rather than an edge: a
-	* stale `expectedVersion` (412) abandons the rest of the queue, so re-read the trash before
-	* offering another attempt.
+	* Purge configurations across components in one bounded fan-out.
 	*
-	* Emptying a trash is the whole-collection case this exists for, which `concurrent`'s default of
-	* 2 would walk through two configurations at a time.
+	* - Stops at the first rejection: a stale `expectedVersion` (412) abandons the rest of the queue,
+	*   so re-read the trash before retrying.
 	*/
 	const purgeConfigurations = async ({ branchId, configs }) => {
 		await concurrent({
@@ -1214,7 +1099,6 @@ const createConfigurations = (client) => {
 			})
 		});
 	};
-	/** Restore a trashed configuration. */
 	const restoreConfiguration = async ({ branchId, componentId, configId }) => {
 		const { data } = await client.post("/v2/storage/branch/{branchId}/components/{componentId}/configs/{configurationId}/restore", { path: {
 			branchId,
@@ -1226,12 +1110,8 @@ const createConfigurations = (client) => {
 	/**
 	* Reset a dev-branch configuration back to its default-branch (production) version.
 	*
-	* The spec is right: the endpoint answers with an empty body, confirmed against the live API by
-	* the nightly smoke (`integration/storageConfigurationLifecycle.smoke.ts`). It used to be typed as
-	* resolving to the configuration, so every caller reading a field off the result was reading
-	* `undefined`. Re-read the configuration to observe the reset.
-	*
-	* Dev-branch only — the API answers 501 on `default`.
+	* - Resolves with an empty body; re-read the configuration to observe the reset.
+	* - Dev-branch only — the API answers 501 on `default`.
 	*/
 	const resetConfigurationToDefault = async ({ branchId, componentId, configId }) => {
 		await client.post("/v2/storage/branch/{branchId}/components/{componentId}/configs/{configurationId}/reset-to-default", { path: {
@@ -1667,18 +1547,11 @@ const createRefreshTokenMiddlware = ({ accessToken, onRefresh }) => {
 //#endregion
 //#region src/clients/storage/search/search.ts
 /**
-* Both responses are asserted in, because the spec stubs them:
+* Search endpoints.
 *
-* - `GET /v2/storage/global-search` (`SearchAction`) declares its 200 as `Record<string, never>` →
-*   really `{ all, items, byType, byProject }`
-* - `GET /v2/storage/search/tables` (`SearchTablesAction`) declares a contentless 200 → really
-*   `Table[]`
-*
-* Both query casts are type-only, so each query object reaches the wire exactly as the caller wrote
-* it. That matters for `global-search`: the spec names its repeatable filters `types[]` / `projectIds[]`
-* / `branchTypes[]` / `branchIds[]`, but this endpoint has always been called with the bare names,
-* which `qs` serializes as `types[0]=bucket&types[1]=table` — also an array to the backend. Renaming
-* the fields to satisfy the document would change what Storage receives, and no test would catch it.
+* - Both responses are asserted in: the spec stubs them.
+* - Query casts are type-only: `global-search` filters go out with bare names (`types`, not
+*   `types[]`); renaming them to match the spec would change what Storage receives.
 */
 const createSearch = (client) => {
 	/**
@@ -1728,8 +1601,7 @@ const createSnapshots = (client) => {
 	/**
 	* Reads a single snapshot. Not branch-scoped — a snapshot id is unique across branches.
 	*
-	* Spec now declares the response, but names the timestamp `createdTime` where `Snapshot` says
-	* `created`, so the shape is still asserted in. It is the same `Snapshot` the table listing returns.
+	* Asserted in: the spec names the timestamp `createdTime`, the API returns `created`.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/GET/v2/storage/snapshots/{snapshotId}
 	*/
@@ -1738,13 +1610,9 @@ const createSnapshots = (client) => {
 		return data;
 	};
 	/**
-	* Deletes a snapshot, returning the storage job that performs it (`null` when the backend answers
-	* with no content). The endpoint is not branch-scoped — a snapshot id is unique across branches, so
-	* there is no `/branch/{branchId}/snapshots/{snapshotId}` variant.
+	* Deletes a snapshot; returns its storage job, or `null` on no content. Not branch-scoped.
 	*
-	* Spec declares the 202 as a `JobResponse` — flat, with `status: string` — where `Job` is a
-	* discriminated union over `status`, and says nothing about the no-content answer, so both are
-	* asserted in.
+	* Asserted in: the spec's flat `JobResponse` is not the discriminated `Job`, and omits no-content.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/DELETE/v2/storage/snapshots/{snapshotId}
 	*/
@@ -1797,10 +1665,8 @@ const createStats = (client) => {
 //#region src/clients/storage/tables/tables.ts
 const createTables = (client, genericClient) => {
 	/**
-	* Returns every table in the given branch. Filter client-side by
-	* `table.bucket?.id` (requires `include: ['buckets']`) or by the
-	* `{bucketId}.` prefix in `table.id` (IDs use `{bucketId}.{tableName}`,
-	* e.g. `in.c-main.users`).
+	* Returns every table in the given branch. Filter by bucket client-side: `table.bucket?.id`
+	* (needs `include: ['buckets']`) or the `{bucketId}.` prefix of `table.id`.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/GET/v2/storage/branch/{branchId}/tables
 	*/
@@ -1868,9 +1734,7 @@ const createTables = (client, genericClient) => {
 	/**
 	* Returns the first rows of a table in the given branch.
 	*
-	* The swagger declares `query?: never` here, so it cannot express `limit` / `whereFilters` /
-	* `orderBy` / `fulltextSearch`, all of which the endpoint accepts — hence the hand-authored
-	* `GetDataPreviewQuery` and the asserted query.
+	* The spec declares `query?: never`, so the query is the hand-written `GetDataPreviewQuery`.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/tables/GET/v2/storage/branch/{branchId}/tables/{tableId}/data-preview
 	*/
@@ -1890,11 +1754,7 @@ const createTables = (client, genericClient) => {
 	/**
 	* Exports a table to a file. Async — returns a job.
 	*
-	* Unbranched, though the document also declares
-	* `/v2/storage/branch/{branchId}/tables/{tableId}/export-async`: export was outside the scope of
-	* the table migration (UT-4785), so switching it would change behaviour for a flow that migration
-	* did not touch. It is the one remaining branch-capable method here that does not take a
-	* `branchId`, and moving it is a clean follow-up.
+	* Unbranched, though a branch-scoped `export-async` exists.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/tables/POST/v2/storage/tables/{tableId}/export-async
 	*/
@@ -1917,7 +1777,7 @@ const createTables = (client, genericClient) => {
 	};
 	/**
 	* Creates a typed table from an explicit column definition (no data) in the given bucket.
-	* The endpoint is async: it returns a `tableDefinitionCreate` storage job the caller can poll.
+	* Async — returns a `tableDefinitionCreate` job.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/buckets/POST/v2/storage/branch/{branchId}/buckets/{bucketId}/tables-definition
 	*/
@@ -1942,14 +1802,10 @@ const createTables = (client, genericClient) => {
 		return data;
 	};
 	/**
-	* Updates a table's definition in place — `displayName`, `description`,
-	* `isDescriptionSystemManaged`, and per-column
-	* `length`/`nullable`/`default`/`description`. The endpoint is async: it
-	* returns a `tableDefinitionUpdate` storage job that the caller can poll.
+	* Updates a table's definition in place. Async — returns a `tableDefinitionUpdate` job.
 	*
-	* Send only the fields being changed; at least one is required. Description
-	* patches apply to non-typed tables too, so a description-only edit needs
-	* neither `displayName` nor `columns`.
+	* - Send only the changed fields; at least one is required.
+	* - Description patches work on non-typed tables too.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/tables/PUT/v2/storage/branch/{branchId}/tables/{tableId}/definition
 	*/
@@ -1964,20 +1820,11 @@ const createTables = (client, genericClient) => {
 		return data;
 	};
 	/**
-	* Updates a table's display name (synchronous). For typed-table column/definition changes use
-	* `updateTableDefinition` instead.
-	*
-	* On the generic client and unbranched, unlike its siblings — but only because of where the
-	* endpoint lives, not because of what it supports. It is still `Storage_TablesController::putAction`
-	* in connection's legacy Zend app, and the Storage document is generated from the `#[OA\...]`
-	* attributes on the migrated Symfony controllers, so no annotation fix closes this gap; the
-	* controller has to move first. The action does take a `DevBranch`, and `put` is in the
-	* branch-implemented route list, so `/branch/{branchId}/tables/{id}` works — there is simply no
-	* `paths` entry to derive it from, and the branch prefix is left to the caller's middleware.
+	* Updates a table's display name (synchronous). Use `updateTableDefinition` for typed tables.
 	*
-	* The synchronous form this calls is deprecated backend-side (`DEPRECATION_SYNC_UPDATE_TABLE` is
-	* logged per request); `?async=true` returns a `tableUpdate` job instead. Switching means polling,
-	* so it belongs with the caller that renames tables, not here.
+	* - Generic client, unbranched: the spec has no path for it; the caller's middleware adds the
+	*   branch prefix.
+	* - The synchronous form is deprecated backend-side; `?async=true` returns a `tableUpdate` job.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/tables
 	*/
@@ -1991,9 +1838,7 @@ const createTables = (client, genericClient) => {
 	/**
 	* Pulls a table from the default branch into the given dev branch.
 	*
-	* The path is branch-scoped: the unbranched `/v2/storage/tables/{id}/pull` this used to call is
-	* absent from the Storage document and 404s for every table (the live nightly caught it), because
-	* nothing in it says which branch to pull into.
+	* Branch-scoped: the unbranched `/v2/storage/tables/{id}/pull` 404s.
 	*
 	* @link https://api.keboola.com/?service=storage#storage/tag/tables
 	*/
@@ -2231,16 +2076,12 @@ const createTriggers = (client) => {
 //#endregion
 //#region src/clients/storage/workspaces/workspaces.ts
 /**
-* Paths, queries and bodies come from the spec; only the returns are asserted in.
+* Paths, queries and bodies come from the spec; only the returns are asserted.
 *
-* - `WorkspaceDetailResponse` describes a narrower connection than callers get, so `Workspace` is
-*   hand-authored (see `./types`) — that covers the list, detail and public-key returns.
+* - `Workspace` is corrected in `./types`: the spec's connection is narrower than callers get.
 * - The password, SSO and delete operations answer a contentless `default`.
-* - `JobResponse` is a flat shape with `status: string`, while `Job<T>` is a discriminated union over
-*   `status` carrying typed `results`.
-*
-* `workspaceId` is a `number` in every input; the operations whose spec segment is a `string` take
-* `String(workspaceId)` here rather than pushing the spec's inconsistency onto callers.
+* - `Job<T>` is a union over `status` with typed `results`; the spec's `JobResponse` is flat.
+* - `workspaceId` is a `number` in every input, stringified where the spec wants a string.
 */
 const createWorkspaces = (client) => {
 	const getWorkspaces = async (path, signal) => {
@@ -2289,9 +2130,7 @@ const createWorkspaces = (client) => {
 		return data;
 	};
 	/**
-	* Set the public key for the workspace user, or migrate workspace from password to key auth.
-	* Supported only on Snowflake.
-	* When called, either a new key is created, or the older one is replaced.
+	* Sets or replaces the workspace user's public key, migrating off password auth. Snowflake only.
 	*/
 	const setWorkspacePublicKey = async ({ branchId, workspaceId, ...body }) => {
 		const { data } = await client.post("/v2/storage/branch/{branchId}/workspaces/{workspaceId}/public-key", {
@@ -2328,10 +2167,9 @@ const createWorkspaces = (client) => {
 		return data;
 	};
 	/**
-	* Preview the resolved load types for a component-style input-mapping config without a workspace.
-	* Returns the preferred load type plus the possible load types per table for the resolved backend,
-	* without creating a job. The backend is resolved per item from the item `backend` field, then the
-	* `backend` argument, then the project default.
+	* Previews the resolved load types for an input-mapping config, without a workspace or job.
+	*
+	* - Backend order: the item's `backend`, then the `backend` argument, then the project default.
 	*/
 	const inputMappingLoadPreview = async ({ branchId, body, backend }, signal) => {
 		const { data } = await client.post("/v2/storage/branch/{branchId}/input-mapping-load/preview", {
@@ -2416,6 +2254,6 @@ const createStorageClient = ({ baseUrl, auth, middlewares = [], onRefreshToken }
 	};
 };
 //#endregion
-export { series as a, ServiceUnavailableError as i, fromBackendSubscribers as n, toBackendSubscribers as r, createStorageClient as t };
+export { readableReason as a, ServiceUnavailableError as i, fromBackendSubscribers as n, series as o, toBackendSubscribers as r, createStorageClient as t };
 
-//# sourceMappingURL=storage-LYwFQPNO.js.map
+//# sourceMappingURL=storage-CZQHZcXG.js.map