@celigo/api-specs 0.2.142 → 0.2.144

package/dist/enduser.yml

@@ -195,7 +195,9 @@ paths:
         '409':
           description: |-
             An end-user record already exists for this user in the account.
-            Error code: `enduser_ashare_exists`.
+            Error code: `enduser_ashare_exists`. A revoked record doesn't count:
+            inviting that address again creates a new record, with none of the
+            old record's groups or grants.
           content:
             application/json:
               schema:
@@ -784,9 +786,12 @@ paths:
       tags:
         - Groups
       description: |-
-        Replaces the group's writable fields. Prefer resending the complete
-        object — omitted fields are not preserved. Requires account owner or
-        administrator access.
+        Replaces the group's writable fields; omitted fields are not preserved.
+        A body with only `name` comes back with no `description`,
+        `resourceGrants: []` and `_roleIds: []`, so the group grants its
+        members nothing while their memberships stay. Read the group first and
+        send its `description`, `_roleIds` and `resourceGrants` back with the
+        change. Requires account owner or administrator access.
       parameters:
         - name: _id
           in: path
@@ -804,9 +809,19 @@ paths:
               $ref: '#/components/schemas/GroupRequest'
             examples:
               rename:
-                summary: Rename the group
+                summary: Rename the group, sending back everything else it holds
                 value:
                   name: Finance EMEA
+                  description: Finance department end users
+                  intendedFor:
+                    - end-user
+                  _roleIds:
+                    - 68c1d2e3f4a5b6c7d8e9f0a1
+                  resourceGrants:
+                    - resourceType: mcpServer
+                      _resourceId: 6a1b2c3d4e5f6a7b8c9d0e1f
+                      capabilities:
+                        - tool:all
       responses:
         '200':
           description: Updated group.
@@ -1133,10 +1148,15 @@ paths:
               $ref: '#/components/schemas/RoleRequest'
             examples:
               updateDescription:
-                summary: Update the description
+                summary: Update the description, sending back the grants it holds
                 value:
                   name: Finance tools
                   description: Updated description
+                  resourceGrants:
+                    - resourceType: mcpServer
+                      _resourceId: 6a1b2c3d4e5f6a7b8c9d0e1f
+                      capabilities:
+                        - pset:6c3d4e5f6a7b8c9d0e1f2a3b
       responses:
         '200':
           description: Updated role.
@@ -1622,7 +1642,7 @@ components:
                   - invite_failed
                 x-enumDescriptions:
                   email_invalid: The email address is not valid
-                  enduser_ashare_exists: An end-user record already exists for this user in the account
+                  enduser_ashare_exists: An end-user record already exists for this user in the account (a revoked record doesn't count)
                   owner_self_invite_not_allowed: The address is the account owner's — owners already have MCP access without an end-user record
                   validation_failed: The shared groupIds or grants failed validation for this item
                   invite_failed: An unexpected per-item error, caught so the batch can continue
@@ -7574,7 +7594,10 @@ components:
       properties:
         updated:
           type: integer
-          description: Number of end-user records updated. Members already in (or absent from) the group are not counted.
+          description: |-
+            Number of listed end users processed, including any already in the
+            group (on add) or already outside it (on remove), whose memberships
+            are left as they were.
     Role:
       type: object
       description: |-

package/dist/filestorage.yml

@@ -389,8 +389,10 @@ paths:
             account. Switches the endpoint to search mode, where `_parentId` is
             ignored and each item carries its `location`. Matches names only, not
             contents or descriptions; a query of several words matches names that
-            contain any of them. Cannot be combined with `name`, `prefix`, or
-            `_integrationId`.
+            contain any of them, and hyphens separate words too, so
+            `orders-2026-q3` also matches every name containing `orders`. To find
+            one item by its exact name, list its folder with `name`. Cannot be
+            combined with `name`, `prefix`, or `_integrationId`.
           schema:
             type: string
             minLength: 2
@@ -834,6 +836,10 @@ paths:
         unknown ids come back inline as
         `{_id, notFound: true, reason: "STORAGE_BATCH_ITEM_NOT_FOUND"}` entries
         alongside the found items.
+
+        Only files are looked up: a folder's id is treated as unknown, so it
+        fails the request or comes back as a `notFound` entry. Read folder
+        metadata from `GET /v1/storage/items`.
       operationId: batchGetStorageItems
       tags:
         - File Storage
@@ -1552,8 +1558,14 @@ paths:
         Merges the contents of a source folder into an existing destination
         folder, then removes the source. Runs asynchronously: the request is
         validated and queued, and the endpoint immediately returns `202` with a
-        job receipt — contents move in the background and the source folder
-        disappears once the merge completes. A soft-deleted source folder may be
+        job receipt — contents move in the background, and the source folder
+        disappears once the merge completes, without passing through the
+        recycle bin. A file whose name is free in the destination moves with its
+        `_id`. A file whose name the destination already holds overwrites that
+        file: the destination file keeps its `_id` and takes the source file's
+        content, its previous content is discarded, and the source file's `_id`
+        is removed — neither goes to the recycle bin, so references to the
+        source file break. A soft-deleted source folder may be
         merged, which restores its contents into the destination. Folders only —
         move individual files with the move endpoint. Requires delete access on
         the source folder and write access on the destination.
@@ -2746,7 +2758,10 @@ components:
             integration's root folder and inherited by everything created inside
             it; null for user-created folders and files at the account root and
             their descendants. Filter the list endpoint with `_integrationId` to
-            scope a listing to one integration.
+            scope a listing to one integration. The root folder is created with
+            the integration and follows it: deleting the integration sends the
+            folder and everything in it to the recycle bin, and purging the
+            integration purges them.
           examples:
             - 6ab1e7ab38d7733b4594d0d2
         integrationName:
@@ -2816,8 +2831,10 @@ components:
           readOnly: true
           description: |-
             When true, the platform created the item (for example a system or
-            integration folder) and protects it — move, content replace, copy,
-            delete, and purge are rejected with `STORAGE_SYSTEM_ITEM_PROTECTED`.
+            integration folder) and protects it — rename, move, content replace,
+            copy, delete, and purge are rejected with 403
+            `STORAGE_SYSTEM_ITEM_PROTECTED` ("System items cannot be modified or
+            deleted").
         deletedAt:
           type: string
           format: date-time

package/dist/mcp-server.yml

@@ -122,7 +122,6 @@ paths:
                         - _id: 6a7b8c9d0e1f2a3b4c5d6e7f
                           name: Finance read-only
                           description: Read-only invoice lookups for the finance team
-                          accessLevel: read
                           _toolIds:
                             - 69d462d5b9c28ea0b7f82522
                           _apiIds: []
@@ -293,7 +292,6 @@ paths:
                       - _id: 6a7b8c9d0e1f2a3b4c5d6e7f
                         name: Finance read-only
                         description: Read-only invoice lookups for the finance team
-                        accessLevel: read
                         _toolIds:
                           - 69d462d5b9c28ea0b7f82522
                         _apiIds: []
@@ -406,7 +404,6 @@ paths:
                     - _id: 6a7b8c9d0e1f2a3b4c5d6e7f
                       name: Finance read-only
                       description: Read-only invoice lookups for the finance team
-                      accessLevel: read
                       _toolIds:
                         - 69d462d5b9c28ea0b7f82522
                       _apiIds: []
@@ -476,7 +473,6 @@ paths:
                       - _id: 6a7b8c9d0e1f2a3b4c5d6e7f
                         name: Finance read-only
                         description: Read-only invoice lookups for the finance team
-                        accessLevel: read
                         _toolIds:
                           - 69d462d5b9c28ea0b7f82522
                         _apiIds: []
@@ -2392,16 +2388,19 @@ components:
         inside the MCP server document, and each set's `_id` is the stable handle
         that grants reference.
 
-        Deleting a set — or resubmitting it without its `_id` — rewrites every
-        grant that references it: the `pset:` capability is replaced with the
-        set's constituent `tool:`, `api:`, `prompt:`, and `resource:`
-        capabilities at removal time.
+        Removing a set — leaving it out of a PUT, or sending it back renamed and
+        without its `_id` — rewrites every end-user, group, and role grant that
+        references it: the `pset:` capability is replaced with the set's
+        constituent `tool:`, `api:`, `prompt:`, and `resource:` capabilities at
+        removal time. The grantees keep that access, but it no longer follows
+        the set: a set created later, even under the same name, reaches none of
+        them until they are granted it.
       x-celigo-ai-guidance:
         - |-
           When updating a server via PUT, send the complete `permissionSets` array
           and round-trip every existing set with its `_id` intact — an omitted set
           is removed and the grants that referenced it are flattened to its
-          individual tool/API capabilities.
+          individual `tool:`, `api:`, `prompt:` and `resource:` capabilities.
       properties:
         _id:
           type: string
@@ -2409,8 +2408,10 @@ components:
           description: |-
             Server-generated identifier for the set — the grant handle referenced
             as `pset:<_id>` in resource grants. Send it back unchanged on PUT to
-            preserve the set's identity; a set submitted without its `_id` is
-            treated as a brand-new set and assigned a fresh one.
+            preserve the set's identity. A set sent without its `_id` keeps the
+            `_id`, and the grants, of the stored set whose `name` matches it
+            (case-insensitively); only a set whose name matches no stored set is
+            new and gets a fresh `_id`.
           examples:
             - 6a7b8c9d0e1f2a3b4c5d6e7f
         name:
@@ -2436,7 +2437,10 @@ components:
           x-enumDescriptions:
             read: Read-level access, aligned with the `mcp:read` OAuth scope
             write: Write-level access, aligned with the `mcp:write` OAuth scope
-          description: OAuth-aligned access level the set pins for everyone it is granted to.
+          description: |-
+            OAuth-aligned access level for the set. The API doesn't store it: a
+            set's reads never include `accessLevel`, so don't rely on it to limit
+            what the set grants.
           examples:
             - read
         _toolIds:
@@ -2492,7 +2496,6 @@ components:
             - - 6aa970882c7f7fbf96a81c5e
       required:
         - name
-        - accessLevel
     UpstreamItemOverrides:
       type: object
       description: |-

package/dist/networkpolicy.yml

@@ -500,9 +500,10 @@ paths:
       description: |-
         Returns the change history for a network policy, newest first. Each entry
         records one event with who made the change, when, and which fields were
-        affected. Entries survive the policy's deletion and purge; the route itself
-        returns 404 once the policy has been purged, so use `GET /v1/audit?resourceType=networkpolicy`
-        to read the history of a purged policy.
+        affected. Entries survive the policy's deletion and purge, but the route
+        itself returns 404 as soon as the policy is deleted, so use
+        `GET /v1/audit?resourceType=networkpolicy` to read the history of a
+        deleted policy.
       tags:
         - Network Policies
       operationId: getNetworkPolicyAudit
@@ -828,7 +829,10 @@ components:
         name:
           type: string
           maxLength: 150
-          description: Display name shown wherever a policy is picked or listed. Unique among the environment's policies that are not in the recycle bin.
+          description: |-
+            Display name shown wherever a policy is picked or listed. Unique among the
+            environment's policies that are not in the recycle bin; on create, a name that
+            differs only in case from a live policy's is accepted.
           examples:
             - Corporate VPN egress
         description:
@@ -929,15 +933,19 @@ components:
           entries fails with 400 `max_cidr_entries_exceeded`. Duplicate entries are stored as sent.
         - |-
           `name` must be unique among the environment's live policies: a duplicate fails with 409
-          `conflict` on create, replace, and patch. A name held only by a policy in the recycle bin
-          can be reused.
+          `conflict` on create, replace, and patch. On create the comparison is case-sensitive: a name
+          that differs from a live policy's only in case is accepted as a separate policy. A name held
+          only by a policy in the recycle bin can be reused.
       required:
         - name
       properties:
         name:
           type: string
           maxLength: 150
-          description: Display name shown wherever a policy is picked or listed. Unique among the environment's policies that are not in the recycle bin.
+          description: |-
+            Display name shown wherever a policy is picked or listed. Unique among the
+            environment's policies that are not in the recycle bin; on create, a name that
+            differs only in case from a live policy's is accepted.
           x-celigo-ai-guidance:
             - Name the policy after the network it describes ("Corporate VPN egress", "Partner SFTP host"), not after the token or MCP server it is assigned to — one policy can be assigned to many principals.
           examples:

package/dist/storagequery.yml

@@ -52,8 +52,10 @@ paths:
         references no file is accepted only when it is a pure constant expression. Supported
         file formats are CSV/TSV, JSON, NDJSON/JSONL, and Parquet; the reader is chosen from
         the file's extension (or its MIME type), and an explicit reader function must match
-        it. A folder is referenced with a trailing slash and contributes its direct child
-        files only; wildcard paths are not supported.
+        it. A compressed file such as `orders.csv.gz` is refused, even through a reader call
+        that passes `compression = 'gzip'`. A folder is referenced with a
+        trailing slash and contributes its direct child files only; wildcard paths are not
+        supported. A file whose upload has not finished yet is refused until it is active.
 
         Read options are named arguments of the reader call, checked against a per-reader
         allowlist — for `read_csv`/`read_csv_auto`: `header`, `delim`, `quote`, `escape`,
@@ -192,7 +194,10 @@ paths:
             catalog-qualified table name, or a path carrying a wildcard
             (`STORAGE_QUERY_INVALID_SOURCE`); a folder path without its trailing slash
             (`STORAGE_NOT_A_FILE`) or a file path with one (`STORAGE_ITEM_NOT_FOLDER`); an
-            unsupported file type (`STORAGE_QUERY_UNSUPPORTED_FILE_TYPE`); a folder that is
+            unsupported file type (`STORAGE_QUERY_UNSUPPORTED_FILE_TYPE`) — a compressed
+            file is refused too, with "Querying `<name>` is not supported; supported formats
+            are CSV, JSON, NDJSON, and Parquet"; a file still uploading ("Upload for `<path>`
+            is not yet complete"); a folder that is
             empty, mixes formats, or holds too many files (`STORAGE_QUERY_FOLDER_EMPTY`,
             `STORAGE_QUERY_MIXED_FORMAT_FOLDER`, `STORAGE_QUERY_FOLDER_TOO_MANY_FILES`); too
             many distinct files (`STORAGE_QUERY_TOO_MANY_SOURCES`); or more input bytes than

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.142",
+  "version": "0.2.144",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "54ef33c9",
+		"iasCommit": "3543542b",
 		"generatedAt": "2026-10-21"
 	},
 	"roots": {