@celigo/api-specs 0.2.140 → 0.2.142

package/dist/ai-agent.yml

@@ -2699,7 +2699,7 @@ components:
             **When to Use**
             - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
             - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-            - NEVER used with simple types (string, number, boolean, date)
+            - NEVER used with simple types (string, number, boolean)
 
             **Behavior**
             - Each mapping in this array becomes a property of the parent object
@@ -3765,7 +3765,7 @@ components:
               **When to Use**
               - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
               - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-              - NEVER used with simple types (string, number, boolean, date)
+              - NEVER used with simple types (string, number, boolean)
 
               **Behavior**
               - Each mapping in this array becomes a property of the parent object

package/dist/api.yml

@@ -3038,16 +3038,19 @@ components:
                     items: {}
                     examples:
                       - - equals
-                        - - get
-                          - customerType
+                        - - string
+                          - - extract
+                            - customerType
                         - premium
                       - - and
-                        - - exists
-                          - - get
-                            - orderId
-                        - - greaterThan
-                          - - get
-                            - amount
+                        - - notempty
+                          - - string
+                            - - extract
+                              - orderId
+                        - - greaterthan
+                          - - number
+                            - - extract
+                              - amount
                           - 1000
                     x-celigo-ai-guidance:
                       - |-
@@ -5260,7 +5263,11 @@ components:
               $ref: '#/components/schemas/AIDescription'
             offline:
               type: boolean
-              description: When true, the connection has been taken offline and is skipped during flow execution.
+              description: |-
+                When true, the connection has been taken offline and is skipped during flow execution.
+                The platform tests the connection after a create or `PUT` and updates this shortly
+                afterwards (the audit log records a `system` change; `lastModified` doesn't move), so
+                read it again a few seconds after the write.
               readOnly: true
             needsAuthorization:
               type: boolean
@@ -7765,9 +7772,8 @@ components:
           ## REQUIRED FIELDS
 
           The Celigo backend rejects the connection POST with HTTP 422 if these
-          type-specific required fields are missing. Rules are enforced by the
-          Mongoose pre-validate hook in
-          `integrator-models/src/models/connection.js`.
+          type-specific required fields are missing. The rules are enforced by
+          server-side validation when the connection is saved.
 
           - `type` — always required; selects the database system.
           - `host` — required for every type EXCEPT `bigquery` and `redshift`.
@@ -8643,7 +8649,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the routing script that returns the target flow.
+              description: Function in the routing script that returns the target flow.
               examples:
                 - routeByDocType
             _scriptId:
@@ -10006,7 +10012,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the referenced script that returns the target flow for each inbound document.
+              description: Function in the referenced script that returns the target flow for each inbound document.
               examples:
                 - contentBasedFlowRouter
             _scriptId:

package/dist/asynchelper.yml

@@ -908,7 +908,7 @@ components:
             **When to Use**
             - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
             - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-            - NEVER used with simple types (string, number, boolean, date)
+            - NEVER used with simple types (string, number, boolean)
 
             **Behavior**
             - Each mapping in this array becomes a property of the parent object
@@ -1974,7 +1974,7 @@ components:
               **When to Use**
               - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
               - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-              - NEVER used with simple types (string, number, boolean, date)
+              - NEVER used with simple types (string, number, boolean)
 
               **Behavior**
               - Each mapping in this array becomes a property of the parent object

package/dist/connection.yml

@@ -1002,6 +1002,7 @@ paths:
         | Path | Description |
         |------|-------------|
         | `/name` | Connection display name |
+        | `/aiDescription` | AI-generated description of the connection |
         | `/debugDate` | Debug logging expiry (ISO-8601, max 1 hour from now) |
         | `/debugUntil` | Alias for `/debugDate` |
         | `/<adaptor>/concurrencyLevel` | Concurrent requests allowed. Platform-managed while `autoRecoverRateLimitErrors` is true — the recovery machinery moves it toward the target, so set `targetConcurrencyLevel` instead |
@@ -1019,8 +1020,10 @@ paths:
         `invalid_field_value`); out-of-range integers are clamped into the account's
         licensed range rather than rejected. A whitelisted path under an adaptor
         block the connection does not use is accepted but never read. The
-        borrowed-from connection must exist in the account, may not itself borrow,
-        and a connection that others borrow from cannot start borrowing.
+        borrowed-from connection must exist in the account and may not itself borrow
+        (422 `connection_borrows_from_another`), and a connection that others borrow
+        from cannot start borrowing (422 `connection_borrowed_by_another`). A
+        connection naming itself is accepted, so check the id before sending it.
         Settings-only changes are recorded in the connection's audit log.
       operationId: patchConnection
       tags:
@@ -4115,7 +4118,11 @@ components:
               $ref: '#/components/schemas/AIDescription'
             offline:
               type: boolean
-              description: When true, the connection has been taken offline and is skipped during flow execution.
+              description: |-
+                When true, the connection has been taken offline and is skipped during flow execution.
+                The platform tests the connection after a create or `PUT` and updates this shortly
+                afterwards (the audit log records a `system` change; `lastModified` doesn't move), so
+                read it again a few seconds after the write.
               readOnly: true
             needsAuthorization:
               type: boolean
@@ -6620,9 +6627,8 @@ components:
           ## REQUIRED FIELDS
 
           The Celigo backend rejects the connection POST with HTTP 422 if these
-          type-specific required fields are missing. Rules are enforced by the
-          Mongoose pre-validate hook in
-          `integrator-models/src/models/connection.js`.
+          type-specific required fields are missing. The rules are enforced by
+          server-side validation when the connection is saved.
 
           - `type` — always required; selects the database system.
           - `host` — required for every type EXCEPT `bigquery` and `redshift`.
@@ -7498,7 +7504,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the routing script that returns the target flow.
+              description: Function in the routing script that returns the target flow.
               examples:
                 - routeByDocType
             _scriptId:
@@ -8861,7 +8867,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the referenced script that returns the target flow for each inbound document.
+              description: Function in the referenced script that returns the target flow for each inbound document.
               examples:
                 - contentBasedFlowRouter
             _scriptId:

package/dist/enduser.yml

@@ -2215,7 +2215,11 @@ components:
               $ref: '#/components/schemas/AIDescription'
             offline:
               type: boolean
-              description: When true, the connection has been taken offline and is skipped during flow execution.
+              description: |-
+                When true, the connection has been taken offline and is skipped during flow execution.
+                The platform tests the connection after a create or `PUT` and updates this shortly
+                afterwards (the audit log records a `system` change; `lastModified` doesn't move), so
+                read it again a few seconds after the write.
               readOnly: true
             needsAuthorization:
               type: boolean
@@ -4720,9 +4724,8 @@ components:
           ## REQUIRED FIELDS
 
           The Celigo backend rejects the connection POST with HTTP 422 if these
-          type-specific required fields are missing. Rules are enforced by the
-          Mongoose pre-validate hook in
-          `integrator-models/src/models/connection.js`.
+          type-specific required fields are missing. The rules are enforced by
+          server-side validation when the connection is saved.
 
           - `type` — always required; selects the database system.
           - `host` — required for every type EXCEPT `bigquery` and `redshift`.
@@ -5598,7 +5601,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the routing script that returns the target flow.
+              description: Function in the routing script that returns the target flow.
               examples:
                 - routeByDocType
             _scriptId:
@@ -6961,7 +6964,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the referenced script that returns the target flow for each inbound document.
+              description: Function in the referenced script that returns the target flow for each inbound document.
               examples:
                 - contentBasedFlowRouter
             _scriptId:

package/dist/export.yml

@@ -6127,7 +6127,12 @@ components:
               - The connection is a cloud file provider used in FOLDER mode (Google Drive, Box, Dropbox,
                 Azure Blob Storage, Google Cloud Storage, Celigo Storage): the export reads the files
                 in a folder and the 'file' object's `type` (csv, json, xml, xlsx, filedefinition)
-                parses each one into records — the same file layer as an FTP or S3 export
+                parses each one into records — the same file layer as an FTP or S3 export. In folder
+                mode `relativeURI` is a folder path: an API endpoint path there fails the run with
+                "Directory is not found. Please create one and provide the path." To download one
+                file per record through the provider's API instead, leave `http.type` unset, set the
+                export's top-level `type` to `blob` (typically on a lookup) and point `relativeURI`
+                at the file-download endpoint
 
               Examples of when to set type: "file":
               - "Download PDF invoices from the API" → type: "file"
@@ -6262,7 +6267,10 @@ components:
           x-celigo-agent:
             - handlebars
           x-celigo-handlebars-context: pre-mapped
-          description: 'Resource path appended to the connection''s `baseURI` to form the complete request URL. Path segments, query parameters, or the entire value can be built with handlebars expressions for endpoints determined at runtime. For lookup exports (`isLookup: true`) with mappings configured, handlebars always render against the original pre-mapped input record, so fields removed or renamed by mappings remain available for URI construction. On `NetSuiteHTTPExport` the base URL is derived from the NetSuite connection and `nsDomainType`, so the path starts at `/services/rest/...` or `/app/site/hosting/restlet.nl`.'
+          description: |-
+            Resource path appended to the connection's `baseURI` to form the complete request URL. Path segments, query parameters, or the entire value can be built with handlebars expressions for endpoints determined at runtime. For lookup exports (`isLookup: true`) with mappings configured, handlebars always render against the original pre-mapped input record, so fields removed or renamed by mappings remain available for URI construction. On `NetSuiteHTTPExport` the base URL is derived from the NetSuite connection and `nsDomainType`, so the path starts at `/services/rest/...` or `/app/site/hosting/restlet.nl`.
+
+            Leave it empty to call the connection's `baseURI` exactly; `/` appends a trailing slash, which is a different URL. An export saved with an empty relative URI and no `http.body` comes back from reads without its `http` block, so a PUT built from such a read loses the stored settings: send the complete `http` block with every PUT.
           x-celigo-ai-guidance:
             - The resource path portion of the API endpoint used for this export.
             - |-
@@ -11121,7 +11129,7 @@ components:
                   webstore: Triggered by SuiteCommerce web store transactions.
                   userevent: Triggered by user event script executions.
                   mapreduce: Triggered by Map/Reduce script operations.
-                  restlet: Triggered by RESTlet API calls.
+                  restlet: Triggered by RESTlet API calls, including the records a NetSuite Distributed import writes.
                   webapplication: Triggered by web application interactions.
                   restwebservices: Triggered by REST web services API calls.
             disabled:
@@ -11129,7 +11137,9 @@ components:
               description: |-
                 When true, the listener's NetSuite deployment is inactive and record saves no longer
                 trigger the export. Maintained by the platform as the flow is disabled and re-enabled;
-                re-enabling the flow re-registers the deployment.
+                re-enabling the flow re-registers the deployment. A listener is created disabled, and
+                a flow created already enabled leaves it that way until a flow update sets
+                `disabled: false`, which activates it within seconds.
               x-celigo-ai-guidance:
                 - |-
                   Pause a listener by disabling its flow, not by setting this field. A listener that has
@@ -12752,7 +12762,7 @@ components:
             **When to Use**
             - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
             - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-            - NEVER used with simple types (string, number, boolean, date)
+            - NEVER used with simple types (string, number, boolean)
 
             **Behavior**
             - Each mapping in this array becomes a property of the parent object
@@ -13818,7 +13828,7 @@ components:
               **When to Use**
               - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
               - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-              - NEVER used with simple types (string, number, boolean, date)
+              - NEVER used with simple types (string, number, boolean)
 
               **Behavior**
               - Each mapping in this array becomes a property of the parent object
@@ -16365,14 +16375,11 @@ components:
 
               **Lookup Exports (isLookup: true)**: Transforms the lookup results returned by the external system.
 
-              ## CRITICAL REQUIREMENT FOR LOOKUPS
+              ## LOOKUPS
 
-              For NetSuite and most other API-based lookups, this field is **ESSENTIAL**. Raw lookup results often come in nested or complex formats that differ from what the flow requires. You **MUST** use a transform to:
-              1. Flatten nested structures (e.g., `results[0].id` -> `id`)
-              2. Map specific fields to the top level
-              3. Handle empty results gracefully
+              Optional on lookups; use one to flatten nested results (e.g., `results[0].id` -> `id`). A lookup's response mapping reads the transformed records, so its extracts name the transformed fields (`data[0].id`), not the raw response paths.
 
-              Note that transformed results are not automatically merged back into source records - merging is handled separately by the 'response mapping' configuration in your flow definition.
+              Transformed results are not merged back into source records automatically; the flow's response mapping does that.
         hooks:
           type: object
           description: |-

package/dist/import.yml

@@ -12929,7 +12929,7 @@ components:
             **When to Use**
             - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
             - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-            - NEVER used with simple types (string, number, boolean, date)
+            - NEVER used with simple types (string, number, boolean)
 
             **Behavior**
             - Each mapping in this array becomes a property of the parent object
@@ -13995,7 +13995,7 @@ components:
               **When to Use**
               - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
               - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-              - NEVER used with simple types (string, number, boolean, date)
+              - NEVER used with simple types (string, number, boolean)
 
               **Behavior**
               - Each mapping in this array becomes a property of the parent object
@@ -16493,8 +16493,9 @@ components:
             - array
             - string
           description: |-
-            Sample response payload used to preview response mappings and test downstream steps
-            without calling the destination system.
+            Sample destination response kept with the import for authoring its response mapping.
+            Flow test runs and previews don't read it; they substitute `mockResponse`, or a
+            placeholder when none is saved.
         responseTransform:
           x-celigo-agent:
             - transform
@@ -16622,7 +16623,9 @@ components:
           description: |-
             Field mappings that transform incoming records into the destination system's field
             structure — renaming fields, converting types, building nested objects, and applying
-            formulas or lookups to derive values.
+            formulas or lookups to derive values. The mapped output builds only the request this
+            import sends: the next step receives the record as it arrived here, plus whatever this
+            step's response mapping merges back.
           x-celigo-ai-guidance:
             - |-
               ## Extract evaluation root

package/dist/mcp-server.yml

@@ -4063,7 +4063,11 @@ components:
               $ref: '#/components/schemas/AIDescription'
             offline:
               type: boolean
-              description: When true, the connection has been taken offline and is skipped during flow execution.
+              description: |-
+                When true, the connection has been taken offline and is skipped during flow execution.
+                The platform tests the connection after a create or `PUT` and updates this shortly
+                afterwards (the audit log records a `system` change; `lastModified` doesn't move), so
+                read it again a few seconds after the write.
               readOnly: true
             needsAuthorization:
               type: boolean
@@ -6568,9 +6572,8 @@ components:
           ## REQUIRED FIELDS
 
           The Celigo backend rejects the connection POST with HTTP 422 if these
-          type-specific required fields are missing. Rules are enforced by the
-          Mongoose pre-validate hook in
-          `integrator-models/src/models/connection.js`.
+          type-specific required fields are missing. The rules are enforced by
+          server-side validation when the connection is saved.
 
           - `type` — always required; selects the database system.
           - `host` — required for every type EXCEPT `bigquery` and `redshift`.
@@ -7446,7 +7449,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the routing script that returns the target flow.
+              description: Function in the routing script that returns the target flow.
               examples:
                 - routeByDocType
             _scriptId:
@@ -8809,7 +8812,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the referenced script that returns the target flow for each inbound document.
+              description: Function in the referenced script that returns the target flow for each inbound document.
               examples:
                 - contentBasedFlowRouter
             _scriptId:

package/dist/tool.yml

@@ -3907,7 +3907,7 @@ components:
             **When to Use**
             - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
             - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-            - NEVER used with simple types (string, number, boolean, date)
+            - NEVER used with simple types (string, number, boolean)
 
             **Behavior**
             - Each mapping in this array becomes a property of the parent object
@@ -4973,7 +4973,7 @@ components:
               **When to Use**
               - REQUIRED when dataType = "object" (unless you are copying an entire object from the input record)
               - REQUIRED in buildArrayHelper.mappings when defining complex object array elements
-              - NEVER used with simple types (string, number, boolean, date)
+              - NEVER used with simple types (string, number, boolean)
 
               **Behavior**
               - Each mapping in this array becomes a property of the parent object
@@ -7446,7 +7446,11 @@ components:
               $ref: '#/components/schemas/AIDescription'
             offline:
               type: boolean
-              description: When true, the connection has been taken offline and is skipped during flow execution.
+              description: |-
+                When true, the connection has been taken offline and is skipped during flow execution.
+                The platform tests the connection after a create or `PUT` and updates this shortly
+                afterwards (the audit log records a `system` change; `lastModified` doesn't move), so
+                read it again a few seconds after the write.
               readOnly: true
             needsAuthorization:
               type: boolean
@@ -9951,9 +9955,8 @@ components:
           ## REQUIRED FIELDS
 
           The Celigo backend rejects the connection POST with HTTP 422 if these
-          type-specific required fields are missing. Rules are enforced by the
-          Mongoose pre-validate hook in
-          `integrator-models/src/models/connection.js`.
+          type-specific required fields are missing. The rules are enforced by
+          server-side validation when the connection is saved.
 
           - `type` — always required; selects the database system.
           - `host` — required for every type EXCEPT `bigquery` and `redshift`.
@@ -10829,7 +10832,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the routing script that returns the target flow.
+              description: Function in the routing script that returns the target flow.
               examples:
                 - routeByDocType
             _scriptId:
@@ -12192,7 +12195,7 @@ components:
           properties:
             function:
               type: string
-              description: Name of the exported function in the referenced script that returns the target flow for each inbound document.
+              description: Function in the referenced script that returns the target flow for each inbound document.
               examples:
                 - contentBasedFlowRouter
             _scriptId:
@@ -25366,8 +25369,9 @@ components:
             - array
             - string
           description: |-
-            Sample response payload used to preview response mappings and test downstream steps
-            without calling the destination system.
+            Sample destination response kept with the import for authoring its response mapping.
+            Flow test runs and previews don't read it; they substitute `mockResponse`, or a
+            placeholder when none is saved.
         responseTransform:
           x-celigo-agent:
             - transform
@@ -25495,7 +25499,9 @@ components:
           description: |-
             Field mappings that transform incoming records into the destination system's field
             structure — renaming fields, converting types, building nested objects, and applying
-            formulas or lookups to derive values.
+            formulas or lookups to derive values. The mapped output builds only the request this
+            import sends: the next step receives the record as it arrived here, plus whatever this
+            step's response mapping merges back.
           x-celigo-ai-guidance:
             - |-
               ## Extract evaluation root
@@ -30523,7 +30529,12 @@ components:
               - The connection is a cloud file provider used in FOLDER mode (Google Drive, Box, Dropbox,
                 Azure Blob Storage, Google Cloud Storage, Celigo Storage): the export reads the files
                 in a folder and the 'file' object's `type` (csv, json, xml, xlsx, filedefinition)
-                parses each one into records — the same file layer as an FTP or S3 export
+                parses each one into records — the same file layer as an FTP or S3 export. In folder
+                mode `relativeURI` is a folder path: an API endpoint path there fails the run with
+                "Directory is not found. Please create one and provide the path." To download one
+                file per record through the provider's API instead, leave `http.type` unset, set the
+                export's top-level `type` to `blob` (typically on a lookup) and point `relativeURI`
+                at the file-download endpoint
 
               Examples of when to set type: "file":
               - "Download PDF invoices from the API" → type: "file"
@@ -30658,7 +30669,10 @@ components:
           x-celigo-agent:
             - handlebars
           x-celigo-handlebars-context: pre-mapped
-          description: 'Resource path appended to the connection''s `baseURI` to form the complete request URL. Path segments, query parameters, or the entire value can be built with handlebars expressions for endpoints determined at runtime. For lookup exports (`isLookup: true`) with mappings configured, handlebars always render against the original pre-mapped input record, so fields removed or renamed by mappings remain available for URI construction. On `NetSuiteHTTPExport` the base URL is derived from the NetSuite connection and `nsDomainType`, so the path starts at `/services/rest/...` or `/app/site/hosting/restlet.nl`.'
+          description: |-
+            Resource path appended to the connection's `baseURI` to form the complete request URL. Path segments, query parameters, or the entire value can be built with handlebars expressions for endpoints determined at runtime. For lookup exports (`isLookup: true`) with mappings configured, handlebars always render against the original pre-mapped input record, so fields removed or renamed by mappings remain available for URI construction. On `NetSuiteHTTPExport` the base URL is derived from the NetSuite connection and `nsDomainType`, so the path starts at `/services/rest/...` or `/app/site/hosting/restlet.nl`.
+
+            Leave it empty to call the connection's `baseURI` exactly; `/` appends a trailing slash, which is a different URL. An export saved with an empty relative URI and no `http.body` comes back from reads without its `http` block, so a PUT built from such a read loses the stored settings: send the complete `http` block with every PUT.
           x-celigo-ai-guidance:
             - The resource path portion of the API endpoint used for this export.
             - |-
@@ -35517,7 +35531,7 @@ components:
                   webstore: Triggered by SuiteCommerce web store transactions.
                   userevent: Triggered by user event script executions.
                   mapreduce: Triggered by Map/Reduce script operations.
-                  restlet: Triggered by RESTlet API calls.
+                  restlet: Triggered by RESTlet API calls, including the records a NetSuite Distributed import writes.
                   webapplication: Triggered by web application interactions.
                   restwebservices: Triggered by REST web services API calls.
             disabled:
@@ -35525,7 +35539,9 @@ components:
               description: |-
                 When true, the listener's NetSuite deployment is inactive and record saves no longer
                 trigger the export. Maintained by the platform as the flow is disabled and re-enabled;
-                re-enabling the flow re-registers the deployment.
+                re-enabling the flow re-registers the deployment. A listener is created disabled, and
+                a flow created already enabled leaves it that way until a flow update sets
+                `disabled: false`, which activates it within seconds.
               x-celigo-ai-guidance:
                 - |-
                   Pause a listener by disabling its flow, not by setting this field. A listener that has
@@ -37359,14 +37375,11 @@ components:
 
               **Lookup Exports (isLookup: true)**: Transforms the lookup results returned by the external system.
 
-              ## CRITICAL REQUIREMENT FOR LOOKUPS
+              ## LOOKUPS
 
-              For NetSuite and most other API-based lookups, this field is **ESSENTIAL**. Raw lookup results often come in nested or complex formats that differ from what the flow requires. You **MUST** use a transform to:
-              1. Flatten nested structures (e.g., `results[0].id` -> `id`)
-              2. Map specific fields to the top level
-              3. Handle empty results gracefully
+              Optional on lookups; use one to flatten nested results (e.g., `results[0].id` -> `id`). A lookup's response mapping reads the transformed records, so its extracts name the transformed fields (`data[0].id`), not the raw response paths.
 
-              Note that transformed results are not automatically merged back into source records - merging is handled separately by the 'response mapping' configuration in your flow definition.
+              Transformed results are not merged back into source records automatically; the flow's response mapping does that.
         hooks:
           type: object
           description: |-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.140",
+  "version": "0.2.142",
   "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": "d5570467",
+		"iasCommit": "54ef33c9",
 		"generatedAt": "2026-10-21"
 	},
 	"roots": {