@celigo/api-specs 0.2.4 → 0.2.6

package/dist/filedefinition.yml

@@ -578,8 +578,38 @@ components:
             profile, e.g. `{{{ediProfile.isa01}}}` or
             `{{{ediProfile.tpInterchangeId}}}`.
 
+            The linked EDI profile's fields resolve under
+            `ediProfile.*`.  X12 profiles: `isa01`, `isa02`, `isa03`,
+            `isa04`, `tpIdQualifier`, `tpInterchangeId`, `myIdQualifier`,
+            `myInterchangeId`, `isa11`, `isa12`, `isa14`, `isa15`,
+            `isa16`, `tpGroupId`, `myGroupId`, `gs07`, `gs08`.  EDIFACT
+            profiles: `unb010_0001`, `unb010_0002`, `tpIdQualifier`,
+            `myIdQualifier`, `tpInterchangeId`, `myInterchangeId`,
+            `versionNumber`, `releaseNumber`, `controllingAgency`.  Both
+            standards also expose the profile's `name`, `description`,
+            `fileType`, and `controlNumber` (the rolling interchange
+            control number — for generate-direction control-number
+            positions such as ISA13).  There are no `isa05`–`isa08`
+            keys: the sender/receiver qualifier and ID positions bind to
+            `tpIdQualifier` / `tpInterchangeId` / `myIdQualifier` /
+            `myInterchangeId` (`tp*` is the trading partner's identity,
+            `my*` is yours — which pair lands in ISA05/06 vs ISA07/08
+            depends on who sends the document).  Field meanings are
+            documented in the EDI Profiles spec.
+
             Use triple-stash (`{{{...}}}`) to avoid HTML escaping for
             EDI control characters.
+          x-celigo-ai-guidance:
+            - |-
+              Never extrapolate positional profile keys: ISA05-ISA08 have no
+              isaNN key — bind them to tpIdQualifier, tpInterchangeId,
+              myIdQualifier, myInterchangeId, choosing the tp*/my* pair by
+              document direction (tp* = trading partner's identity).
+            - |-
+              A referenceValue naming a key outside the profile's field set
+              saves without error but fails at parse/preview time with
+              "Handlebar expression pattern is incorrect. Please correct it
+              to an appropriate pattern for : <key>".
           examples:
             - '{{{ediProfile.isa01}}}'
             - '{{{ediProfile.tpInterchangeId}}}'

package/dist/job.yml

@@ -1707,8 +1707,16 @@ components:
             Omitting `time_gt` does not mean "all history" — the endpoint falls back to the dashboard's
             default window (approximately the last 24 hours), and runs older than that silently drop out
             of every aggregate. Send `time_gt` (epoch milliseconds) explicitly for any other range.
+
+            `time_lte` must not be later than the current time: a future value is rejected with
+            `400 invalid_filter_request_body` (unlike `POST /v1/jobs/current`, which accepts it). Omit
+            `time_lte` to end the window at now. When both bounds are sent they must be at least one hour
+            apart (`time_lte - time_gt >= 3600000`), or the request is rejected with
+            `400 invalid_time_filter`; a window with `time_gt` alone has no minimum span.
           x-celigo-ai-guidance:
             - Always send an explicit time_gt matching the window you intend to report, and never present the aggregates as covering a longer period than the time filter you sent. Without time_gt the default window (~24 hours) applies — an empty result then means "nothing ran recently", never "no runs exist".
+            - For a window that runs through the present, omit time_lte rather than computing an end bound — a value even seconds ahead of the server clock (a rounded-up "now", end of today) fails the whole request with 400 invalid_filter_request_body.
+            - A closed window narrower than one hour cannot be queried; widen time_lte to time_gt + one hour (and say so when reporting) rather than sending the narrower range.
             - A flow absent from stats[] had no runs in the window; it does not mean the flow does not exist. numOpenError counts errors open NOW, which may predate the window.
     FlowRunStatsEntry:
       type: object

package/package.json

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

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "6f06402",
-		"generatedAt": "2026-09-05"
+		"iasCommit": "96fa282",
+		"generatedAt": "2026-09-10"
 	},
 	"roots": {
 		"aiagent": 121,