The Action an entity-change trigger dispatches to.
Execute Agent already exists and was written for exactly this: "a concrete dispatch target for
AIAgent.ExposeAsAction". Entity-action invocation is likewise already wired — the save pipeline
fires validate / before-save / after-save / before-delete / after-delete through
HandleEntityActions. So an entity-change trigger needs no new machinery at all; it needs a
binding row, which is what this creates.
The Action an entity-change trigger dispatches to.
Execute Agentalready exists and was written for exactly this: "a concrete dispatch target forAIAgent.ExposeAsAction". Entity-action invocation is likewise already wired — the save pipeline fires validate / before-save / after-save / before-delete / after-delete throughHandleEntityActions. So an entity-change trigger needs no new machinery at all; it needs a binding row, which is what this creates.