@celigo/api-specs 0.2.52 → 0.2.53

package/dist/import.yml

@@ -1605,7 +1605,17 @@ components:
           description: Internal flag indicating the import was built with the legacy REST form rather than the unified HTTP framework. Set by the form; not configured directly.
         strictHandlebarEvaluation:
           type: boolean
-          description: When true, handlebars expressions that reference a missing field raise an error instead of rendering an empty string, surfacing mapping mistakes early rather than sending blank values.
+          description: Intended to make handlebars expressions that reference a missing field raise an error instead of rendering an empty string. In live runs on an HTTP import it does not have that effect on `http.body` templates or mapping expressions — an undefined path still renders empty and the record succeeds with the flag true — and `relativeURI` / `headers[].value` templates already fail on an undefined path regardless of this flag. Not a safeguard against a wrong template root or a misspelled path.
+          x-celigo-ai-guidance:
+            - |-
+              Do not rely on this flag to catch a mis-rooted or misspelled path. Live-verified
+              2026-09-24 on an HTTP import in real flow runs with the flag ``true``: an undefined
+              ``{{record.<field>}}`` in ``http.body`` and an undefined ``{{<field>}}`` in a mapping
+              expression both rendered empty and the record succeeded — the same outcome as with
+              the flag ``false`` or unset. Relative URI and header templates fail on an undefined
+              path regardless of this flag. To catch a wrong root, check the template against the
+              record's shape (``record`` for an object, ``rows`` for a grouped record,
+              ``batch_of_records`` when ``batchSize`` exceeds 1) before saving.
         formType:
           type: string
           enum:
@@ -2020,10 +2030,12 @@ components:
               nor ``rows`` exists at the top level. Inside ``data`` a grouped record is itself an
               array element (``{{#each data}}{{#each this}}…{{/each}}{{/each}}``). An object record
               that carries its own ``rows`` field is still ``record`` — ``{{#each record.rows}}``.
-              Here an undefined path renders empty by default (``strictHandlebarEvaluation`` is the
-              documented switch to raise instead); in ``relativeURI`` and ``headers[].value``
-              templates an undefined path always fails the request — a wrong root there is a
-              runtime failure, not a blank.
+              Here an undefined path renders empty — and ``strictHandlebarEvaluation: true`` does
+              not change that (live-verified 2026-09-24 in real flow runs: an undefined
+              ``{{record.<field>}}`` in the body rendered empty and the record succeeded); in
+              ``relativeURI`` and ``headers[].value`` templates an undefined path always fails the
+              request — a wrong root there is a runtime failure, not a blank. Verify the body's
+              root against the record shape; no flag will catch it.
             - |-
               ## LEAVE UNDEFINED for the most common case
 

package/dist/tool.yml

@@ -12125,7 +12125,17 @@ components:
           description: Internal flag indicating the import was built with the legacy REST form rather than the unified HTTP framework. Set by the form; not configured directly.
         strictHandlebarEvaluation:
           type: boolean
-          description: When true, handlebars expressions that reference a missing field raise an error instead of rendering an empty string, surfacing mapping mistakes early rather than sending blank values.
+          description: Intended to make handlebars expressions that reference a missing field raise an error instead of rendering an empty string. In live runs on an HTTP import it does not have that effect on `http.body` templates or mapping expressions — an undefined path still renders empty and the record succeeds with the flag true — and `relativeURI` / `headers[].value` templates already fail on an undefined path regardless of this flag. Not a safeguard against a wrong template root or a misspelled path.
+          x-celigo-ai-guidance:
+            - |-
+              Do not rely on this flag to catch a mis-rooted or misspelled path. Live-verified
+              2026-09-24 on an HTTP import in real flow runs with the flag ``true``: an undefined
+              ``{{record.<field>}}`` in ``http.body`` and an undefined ``{{<field>}}`` in a mapping
+              expression both rendered empty and the record succeeded — the same outcome as with
+              the flag ``false`` or unset. Relative URI and header templates fail on an undefined
+              path regardless of this flag. To catch a wrong root, check the template against the
+              record's shape (``record`` for an object, ``rows`` for a grouped record,
+              ``batch_of_records`` when ``batchSize`` exceeds 1) before saving.
         formType:
           type: string
           enum:
@@ -12540,10 +12550,12 @@ components:
               nor ``rows`` exists at the top level. Inside ``data`` a grouped record is itself an
               array element (``{{#each data}}{{#each this}}…{{/each}}{{/each}}``). An object record
               that carries its own ``rows`` field is still ``record`` — ``{{#each record.rows}}``.
-              Here an undefined path renders empty by default (``strictHandlebarEvaluation`` is the
-              documented switch to raise instead); in ``relativeURI`` and ``headers[].value``
-              templates an undefined path always fails the request — a wrong root there is a
-              runtime failure, not a blank.
+              Here an undefined path renders empty — and ``strictHandlebarEvaluation: true`` does
+              not change that (live-verified 2026-09-24 in real flow runs: an undefined
+              ``{{record.<field>}}`` in the body rendered empty and the record succeeded); in
+              ``relativeURI`` and ``headers[].value`` templates an undefined path always fails the
+              request — a wrong root there is a runtime failure, not a blank. Verify the body's
+              root against the record shape; no flag will catch it.
             - |-
               ## LEAVE UNDEFINED for the most common case
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.52",
+  "version": "0.2.53",
   "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": "b5bc8d2",
+		"iasCommit": "5cccadb",
 		"generatedAt": "2026-09-24"
 	},
 	"roots": {