@celigo/api-specs 0.2.155 → 0.2.157

package/dist/ediprofile.yml

@@ -412,7 +412,10 @@ components:
           description: |-
             Trading partner's interchange identifier: the sender ID on files the partner sends and the
             receiver ID on files you send (X12 ISA06 and ISA08 respectively; the UNB sender and
-            recipient in EDIFACT).
+            recipient in EDIFACT). On an X12 profile, store it unpadded: parsing compares an inbound
+            file's ISA06 without its padding, so a value padded to 15 characters fails every inbound
+            file (`Interchange Sender ID with data <id> in the EDI file doesn't match with the expected
+            data in the EDI profile.`).
           examples:
             - ACMECORP
             - '5412345678901'
@@ -421,7 +424,10 @@ components:
           description: |-
             Your interchange identifier: the receiver ID on files the partner sends and the sender ID
             on files you send (X12 ISA08 and ISA06 respectively; the UNB recipient and sender in
-            EDIFACT).
+            EDIFACT). On an X12 profile, store it unpadded: parsing compares an inbound file's ISA08
+            without its padding, so a value padded to 15 characters fails every inbound file
+            (`Interchange Receiver ID with data <id> in the EDI file doesn't match with the expected
+            data in the EDI profile.`).
           examples:
             - MYCOMPANY
             - '1234567890123'
@@ -462,7 +468,7 @@ components:
           description: |-
             X12 ISA02 — Authorization Information. When parsing, an inbound file's ISA02 must match
             this value after trimming (`data_mismatch` otherwise), so a blank ISA02 matches `""` and
-            not ten spaces.
+            not ten spaces or one (values some trading partner connector forms prescribe).
           examples:
             - ''
         isa03:
@@ -481,7 +487,7 @@ components:
           description: |-
             X12 ISA04 — Security Information. When parsing, an inbound file's ISA04 must match this
             value after trimming (`data_mismatch` otherwise), so a blank ISA04 matches `""` and not
-            ten spaces.
+            ten spaces or one (values some trading partner connector forms prescribe).
           examples:
             - ''
         tpIdQualifier:

package/dist/filedefinition.yml

@@ -497,6 +497,10 @@ components:
             record); for the row-type marker, equals `value` (in a
             container's child rule, a marker whose `name` differs from
             its `value` parses to an empty record without an error).
+            Names must be unique within a rule's `elements`: a save or a
+            parse with two of the same name is refused (`Sibling element
+            names need to be unique. Duplicate "<name>" found in
+            elements: [<i>, <j>]`).
           examples:
             - Order ID
             - Authorization Information Qualifier
@@ -569,13 +573,30 @@ components:
             Inclusive minimum string length.  Used heavily on EDI
             elements where the X12 / EDIFACT standard fixes the length
             of envelope qualifiers (e.g. `ISA05` is exactly 2 chars,
-            `ISA13` is exactly 9 chars).
+            `ISA13` is exactly 9 chars).  A parse refuses a shorter value
+            (`Min. length not met for the field "ISA06"`).  Generation
+            doesn't pad to it; see `maxLength`.
         maxLength:
           type: integer
           minimum: 0
           description: |
             Inclusive maximum string length.  See `minLength` for
             usage notes.
+
+            Generation pads a shorter non-empty value with spaces up to
+            `maxLength` (`minLength` doesn't pad).  An empty value stays
+            empty, except on ISA02/ISA04 elements that keep their
+            standard names (`Authorization Information`, `Security
+            Information`), which are written as `maxLength` spaces.  So a
+            generate definition keeps the fixed-width X12 ISA at full
+            width (ISA02/ISA04 10 characters, ISA06/ISA08 15, 106
+            characters with the terminator) only with `maxLength` on
+            those elements.  Without it, a blank `isa02` comes out empty
+            and an unpadded interchange id short, and Celigo's own parser
+            refuses that ISA (`Mandatory element "ISA02" is not present`,
+            `Min. length not met for the field "ISA06"`).  A value longer
+            than `maxLength` fails the generation (`Max. length not met
+            for the field "<name>"`).
         referenceValue:
           type: string
           description: |
@@ -660,6 +681,14 @@ components:
             assigned numbers, HL hierarchical ids).
           examples:
             - true
+        ignore:
+          type: boolean
+          description: |
+            When true, the parser reads the element (on a fixed-width row
+            it still takes its `length`) but leaves it out of the parsed
+            record.
+          examples:
+            - true
         startPosition:
           type: integer
           minimum: 1
@@ -793,7 +822,7 @@ components:
             per segment-element (`ISA01`, `ISA02`, ...).  Delimited
             rules use one element per column.  Omit the key on a rule
             with no elements of its own, such as a container wrapper: an
-            empty `elements` array fails the parse.
+            empty `elements` array saves, but fails the parse.
           items:
             $ref: '#/components/schemas/Element'
         children:
@@ -821,6 +850,11 @@ components:
             round-trips file definitions should preserve whichever shape
             the source document uses.
 
+            Put it on the rule that opens the envelope (ISA, GS, ST, UNB,
+            UNH), never on a `container` wrapper.  A container's close rule
+            saves and parses without an error, but it consumes the row it
+            names, so the rule meant to read that row comes back empty.
+
             For non-EDI / non-loop rules `closeRule` is omitted.
           oneOf:
             - title: rule
@@ -841,10 +875,15 @@ components:
             under the wrapper's `name`; `container: true` on a rule with
             its own `elements` isn't honored as a loop.
 
-            The parser rejects `container: true` paired with
-            `maxOccurrence <= 1` with
-            `Invalid rules: maxOccurences should be greater than '1',
-            when the container is 'true'`.
+            A container repeats up to its `maxOccurrence`, which defaults
+            to `1`.  A container with `1`, or without the key, saves and
+            parses but matches a single row: in fixed-width and delimited
+            files the rows after it are dropped without an error, and an
+            X12 parse fails at the next row it can't place, naming a
+            mandatory segment as missing (for example `Mandatory segment
+            "SE" is missing on line: 6`).  A rule outside any container
+            matches one row the same way.  Give the wrapper the most rows
+            the file can hold, such as `1000`.
           default: false
           examples:
             - true
@@ -859,8 +898,12 @@ components:
             an `ST` transaction set or a line-item loop; EDI envelopes use
             `1` (one ISA per file, one GS per group).
 
-            Required to be greater than `1` when `container` is
-            `true`.
+            Defaults to `1`, so a container needs a larger value to repeat
+            (see `container`).  A value above `1` on any other rule saves,
+            but the parse refuses it with `Max no. of occurrences for
+            segment "<name>" is applicable only if it is a
+            container/loop.`  `0` is refused on save and on parse (`if
+            present, maxOccurrence must be greater than or equal to 1`).
           examples:
             - 1
             - 1000
@@ -928,6 +971,16 @@ components:
               - P,04,05
             - - L,03,04,05,13
               - R,02,03
+        ignoreIdentifier:
+          type: boolean
+          description: |
+            Fixed-width: the rule matches rows without looking for a
+            row-type marker.  Set it on the row rule of a file whose rows
+            carry no marker, inside a `container` so every row is read.
+            Without it such rows parse to one empty record (`{}`) with no
+            error, wrapped or not.
+          examples:
+            - true
     FileDefinitionBase:
       type: object
       description: Writable file definition fields shared by the request and response schemas.
@@ -1131,8 +1184,10 @@ components:
         - |-
           Rows repeat only under an elements-less `container: true` rule (a group `name`,
           `maxOccurrence` above 1, no `elements`) whose child rule carries the row's elements. A
-          row-marker rule with no such container above it matches only the first row, and the parser
-          drops the rest without an error.
+          row-marker rule with no such container above it, or under a container whose
+          `maxOccurrence` is 1 or unset, matches only the first row: in fixed-width and delimited
+          files the parser drops the rest without an error, and an X12 parse fails at the next row,
+          naming a mandatory segment as missing.
     ResourceResponse:
       type: object
       description: Response

package/dist/guardrail.yml

@@ -593,9 +593,10 @@ components:
       description: |
         LLM configuration for an `ai_agent` guardrail — which provider and model evaluate each
         record, with instructions, parameter tuning, and output format. Guardrails never invoke
-        tools, so unlike an AI agent import no block here accepts a `tools` array; MCP `prompts`
-        and `resources` remain available. Providers come in two families with two configuration
-        formats:
+        tools, so unlike an AI agent import no block here accepts a `tools` array. MCP `prompts`
+        and `resources` are accepted on save, but an unreachable MCP server doesn't fail the
+        run (verified on OpenAI), so put the policy the guardrail must apply in its
+        instructions. Providers come in two families with two configuration formats:
 
         - **Built-in providers** — each has its own configuration block.
           - **openai**: OpenAI models (GPT-4.1, GPT-5, etc.). Configure via the `openai` object.
@@ -759,7 +760,7 @@ components:
         prompts:
           type: array
           description: |-
-            MCP prompt entries available to a catalog-provider guardrail (generic flat format).
+            MCP prompt entries saved with a catalog-provider guardrail (generic flat format).
             Each entry references one MCP connection and the prompt names allowed from it.
           items:
             type: object
@@ -815,7 +816,6 @@ components:
                 - gpt-5-mini
                 - gpt-5-nano
                 - gpt-4.1-mini
-                - gpt-4o
               x-celigo-ui-override: Required by the AI agent configuration form. Encoded here to mirror the form so builders produce connectable configurations.
               x-celigo-ai-guidance:
                 - |-
@@ -1038,7 +1038,7 @@ components:
             prompts:
               type: array
               description: |-
-                MCP prompt entries available to the guardrail's model. Each item references one
+                MCP prompt entries saved with the guardrail. Each item references one
                 MCP connection and the prompt names allowed from it.
               items:
                 type: object
@@ -1227,7 +1227,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Gemini model. Each item references one
+                        MCP prompt entries saved with a Gemini guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -1449,7 +1449,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Claude model. Each item references one
+                        MCP prompt entries saved with a Claude guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -1543,7 +1543,11 @@ components:
           Guardrails never invoke tools. A non-empty `tools` array anywhere under `aiAgent`
           (`aiAgent.tools`, `aiAgent.openai.tools`, `aiAgent.litellm._overrides.gemini.tools`,
           `aiAgent.litellm._overrides.anthropic.tools`) fails the save with 422
-          `guardrail_tools_not_allowed`; MCP `prompts` and `resources` are still accepted.
+          `guardrail_tools_not_allowed`. MCP `prompts` and `resources` are still accepted on
+          save, but don't rely on them for the check: with their MCP server unreachable, a
+          guardrail runs on its instructions and input alone, with no error, where an AI agent's
+          run fails (verified on OpenAI). Put the policy the guardrail must apply in its
+          instructions.
       properties:
         type:
           type: string

package/dist/import.yml

@@ -10668,9 +10668,10 @@ components:
       description: |
         LLM configuration for an `ai_agent` guardrail — which provider and model evaluate each
         record, with instructions, parameter tuning, and output format. Guardrails never invoke
-        tools, so unlike an AI agent import no block here accepts a `tools` array; MCP `prompts`
-        and `resources` remain available. Providers come in two families with two configuration
-        formats:
+        tools, so unlike an AI agent import no block here accepts a `tools` array. MCP `prompts`
+        and `resources` are accepted on save, but an unreachable MCP server doesn't fail the
+        run (verified on OpenAI), so put the policy the guardrail must apply in its
+        instructions. Providers come in two families with two configuration formats:
 
         - **Built-in providers** — each has its own configuration block.
           - **openai**: OpenAI models (GPT-4.1, GPT-5, etc.). Configure via the `openai` object.
@@ -10834,7 +10835,7 @@ components:
         prompts:
           type: array
           description: |-
-            MCP prompt entries available to a catalog-provider guardrail (generic flat format).
+            MCP prompt entries saved with a catalog-provider guardrail (generic flat format).
             Each entry references one MCP connection and the prompt names allowed from it.
           items:
             type: object
@@ -10890,7 +10891,6 @@ components:
                 - gpt-5-mini
                 - gpt-5-nano
                 - gpt-4.1-mini
-                - gpt-4o
               x-celigo-ui-override: Required by the AI agent configuration form. Encoded here to mirror the form so builders produce connectable configurations.
               x-celigo-ai-guidance:
                 - |-
@@ -11113,7 +11113,7 @@ components:
             prompts:
               type: array
               description: |-
-                MCP prompt entries available to the guardrail's model. Each item references one
+                MCP prompt entries saved with the guardrail. Each item references one
                 MCP connection and the prompt names allowed from it.
               items:
                 type: object
@@ -11302,7 +11302,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Gemini model. Each item references one
+                        MCP prompt entries saved with a Gemini guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -11524,7 +11524,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Claude model. Each item references one
+                        MCP prompt entries saved with a Claude guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -11649,7 +11649,9 @@ components:
           `aiAgent.openai.tools`, `aiAgent.litellm._overrides.gemini.tools`, `….anthropic.tools`) —
           any non-empty array fails the save with 422 `guardrail_tools_not_allowed` ("Tools aren't
           supported on a guardrail AI agent configuration…"), on create and on update. `prompts` and
-          `resources` are accepted; the server still echoes `openai.tools: []` on OpenAI guardrails.
+          `resources` are accepted on save, but an unreachable MCP server doesn't fail the run
+          (verified on OpenAI), so put the policy in the instructions. The server still echoes
+          `openai.tools: []` on OpenAI guardrails.
       properties:
         type:
           type: string

package/dist/tool.yml

@@ -22136,9 +22136,10 @@ components:
       description: |
         LLM configuration for an `ai_agent` guardrail — which provider and model evaluate each
         record, with instructions, parameter tuning, and output format. Guardrails never invoke
-        tools, so unlike an AI agent import no block here accepts a `tools` array; MCP `prompts`
-        and `resources` remain available. Providers come in two families with two configuration
-        formats:
+        tools, so unlike an AI agent import no block here accepts a `tools` array. MCP `prompts`
+        and `resources` are accepted on save, but an unreachable MCP server doesn't fail the
+        run (verified on OpenAI), so put the policy the guardrail must apply in its
+        instructions. Providers come in two families with two configuration formats:
 
         - **Built-in providers** — each has its own configuration block.
           - **openai**: OpenAI models (GPT-4.1, GPT-5, etc.). Configure via the `openai` object.
@@ -22302,7 +22303,7 @@ components:
         prompts:
           type: array
           description: |-
-            MCP prompt entries available to a catalog-provider guardrail (generic flat format).
+            MCP prompt entries saved with a catalog-provider guardrail (generic flat format).
             Each entry references one MCP connection and the prompt names allowed from it.
           items:
             type: object
@@ -22358,7 +22359,6 @@ components:
                 - gpt-5-mini
                 - gpt-5-nano
                 - gpt-4.1-mini
-                - gpt-4o
               x-celigo-ui-override: Required by the AI agent configuration form. Encoded here to mirror the form so builders produce connectable configurations.
               x-celigo-ai-guidance:
                 - |-
@@ -22581,7 +22581,7 @@ components:
             prompts:
               type: array
               description: |-
-                MCP prompt entries available to the guardrail's model. Each item references one
+                MCP prompt entries saved with the guardrail. Each item references one
                 MCP connection and the prompt names allowed from it.
               items:
                 type: object
@@ -22770,7 +22770,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Gemini model. Each item references one
+                        MCP prompt entries saved with a Gemini guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -22992,7 +22992,7 @@ components:
                     prompts:
                       type: array
                       description: |-
-                        MCP prompt entries available to the Claude model. Each item references one
+                        MCP prompt entries saved with a Claude guardrail. Each item references one
                         MCP connection and the prompt names allowed from it.
                       items:
                         type: object
@@ -23117,7 +23117,9 @@ components:
           `aiAgent.openai.tools`, `aiAgent.litellm._overrides.gemini.tools`, `….anthropic.tools`) —
           any non-empty array fails the save with 422 `guardrail_tools_not_allowed` ("Tools aren't
           supported on a guardrail AI agent configuration…"), on create and on update. `prompts` and
-          `resources` are accepted; the server still echoes `openai.tools: []` on OpenAI guardrails.
+          `resources` are accepted on save, but an unreachable MCP server doesn't fail the run
+          (verified on OpenAI), so put the policy in the instructions. The server still echoes
+          `openai.tools: []` on OpenAI guardrails.
       properties:
         type:
           type: string

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.155",
+  "version": "0.2.157",
   "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": "37aee3d1",
+		"iasCommit": "063d41cc",
 		"generatedAt": "2026-10-21"
 	},
 	"roots": {
@@ -5575,6 +5575,7 @@
 				"container": 9,
 				"description": 1,
 				"elements": 476,
+				"ignoreIdentifier": 9,
 				"maxOccurrence": 125,
 				"name": 1,
 				"relationship": 21,
@@ -5593,6 +5594,7 @@
 				"description": 1,
 				"end": 125,
 				"enum": 21,
+				"ignore": 9,
 				"length": 125,
 				"maxLength": 125,
 				"minLength": 125,