@celigo/api-specs 0.2.21 → 0.2.22

package/dist/ai-agent.yml

@@ -4951,13 +4951,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -4987,8 +5000,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)

package/dist/export.yml

@@ -803,13 +803,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -839,8 +852,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)

package/dist/import.yml

@@ -10581,13 +10581,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -10617,8 +10630,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)

package/dist/tool.yml

@@ -19439,13 +19439,26 @@ components:
         are re-joined into the record's original shape — the object with its array, or the array of rows —
         carrying any response-mapping enrichment, and that re-joined record is what the next step
         receives. Not for locating records in an export's HTTP response; use
-        `http.response.resourcePath` for that.
+        `http.response.resourcePath` for that. Applies to steps that receive a record — imports and
+        lookups (an export referenced as a page processor of a flow, API, or Tool). A standalone export
+        (a flow's page generator) has no incoming record, so the fields are saved but have no effect on
+        the records it produces; to emit one record per array element from a standalone export, use a
+        `hooks.preSavePage` script, or for a file-definition export make the repeating segment the
+        record boundary in the definition's rules.
       x-celigo-ai-guidance:
         - |-
           Two modes, decided by the SHAPE of the record entering the step. Object record with a child
           array under a field → set ``pathToMany`` to that field. Array record (a ``groupByFields``
           export, a CSV/file group, a script that returns an array) → leave ``pathToMany`` blank; each
           element becomes one record. Live-verified 2026-09-10 on flows, Tools, and APIs.
+        - |-
+          Only imports and lookups (exports placed as page processors) fan out. On a standalone export
+          (a flow's page generator) the API saves ``oneToMany`` / ``pathToMany`` and applies neither:
+          the records reach the next step unchanged and no error is raised. Live-verified 2026-09-18 on
+          a flow test run — an order record with three ``lines`` reached the import as ONE record with
+          the setting on the export, and as THREE child records with the same setting on the import.
+          Never propose these fields as the way to split a standalone export's records; that is
+          ``hooks.preSavePage`` work (or, for a file definition, the definition's record boundary).
         - |-
           Blank ``pathToMany`` on an OBJECT record fails every record with code ``oneToMany_error``:
           "Failed to extract child records from oneToMany import data. Record at index 0 was not an
@@ -19475,8 +19488,14 @@ components:
         Path to the array of child records inside an object record when `oneToMany` is true, in dot
         notation (`items`, `lines.lineItems`). Leave blank when the incoming record is itself an array
         (grouped or row-based data) — each element is then a child record. A path that does not resolve
-        to an array processes zero records and reports success.
+        to an array processes zero records and reports success. Read only on steps that receive a
+        record (imports, lookup exports); on a standalone export it is saved and ignored — see `oneToMany`.
       x-celigo-ai-guidance:
+        - |-
+          Inert on a standalone export (a flow's page generator) exactly like ``oneToMany`` — the value
+          is saved, the export's records reach the next step unchanged, and nothing errors
+          (live-verified 2026-09-18). Splitting a standalone export's records into one per element is
+          ``hooks.preSavePage`` work, or the file definition's record boundary; never this field.
         - |-
           Set this ONLY when the record entering the step is an object whose children sit under a field.
           On an array record (a ``groupByFields`` export, a CSV/file group, a script returning an array)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.21",
+  "version": "0.2.22",
   "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": "dc9205a",
+		"iasCommit": "c51aefb",
 		"generatedAt": "2026-09-18"
 	},
 	"roots": {