chore(automation-client, event-catalog-client): Event Catalog trigger support

.changeset/automation-client-event-catalog-trigger.md

@@ -0,0 +1,10 @@
+---
+"@epilot/automation-client": minor
+---
+
+Add Event Catalog trigger support
+
+- `EventCatalogTrigger` (`type: event_catalog`) — starts a flow when an Event Catalog event is published; pinned to an `event_version`, runs in the context of the entity behind `entity_node_id`, `ignore_automation_triggered` defaults to `true`
+- `TriggerEventEventCatalog` — new `AutomationExecution.trigger_event` variant with `event_id`, `event_name`, `event_version`, `published_version`, `entity_node_id` and a `payload_ref` to the stored payload
+- `ConditionStatement.source.originType` accepts `event` to read the operand from the trigger's event payload
+- `searchFlows` accepts a `trigger_event_name` query parameter to filter flows by Event Catalog event

.changeset/event-catalog-client-automation-chain.md

@@ -0,0 +1,7 @@
+---
+"@epilot/event-catalog-client": patch
+---
+
+Add `_automation_chain` to `TriggerEventPayload` and `Event`
+
+Optional ordered list of automation flow ids that caused the trigger. It is propagated verbatim onto the published event so that automations started by Event Catalog events can detect and break automation loops.

clients/automation-client/src/openapi-runtime.json

@@ -29,6 +29,10 @@
             "name": "target_workflow",
             "in": "query"
           },
+          {
+            "name": "trigger_event_name",
+            "in": "query"
+          },
           {
             "name": "include_flows",
             "in": "query"