feat(workflow-executor): add TriggerActionStepExecutor with confirmation flow

[Scra3]

Summary

• Implements TriggerActionStepExecutor following the UpdateRecordStepExecutor pattern (branches A/B/C, automaticExecution, confirmation flow)
• AI selects an action via a select-action tool (Zod enum of display names + technical names as hints); resolveActionName maps displayName → technical name with name fallback
• Adds TriggerActionStepExecutionData with executionParams: { actionDisplayName, actionName }, executionResult: { success } | { skipped }, and pendingAction for the awaiting-confirmation state
• Adds NoActionsError for collections with no actions
• Fixes buildStepSummary in BaseStepExecutor to include trigger-action pendingAction in prior-step AI context (parity with update-record pendingUpdate)
• Action result intentionally discarded — privacy constraint (no client data leaves the infrastructure)

Test plan

• Branch B (automaticExecution: true) — triggers action, saves executionParams with both display and technical name, returns success
• Branch C (no automaticExecution) — saves pendingAction, returns awaiting-input
• Branch A confirmed — triggers action, preserves pendingAction for traceability
• Branch A rejected — action not called, saves { skipped: true }
• Branch A no pending action — throws
• NoActionsError — returns error outcome
• WorkflowExecutorError from executeAction → error outcome (branches A & B)
• Infrastructure errors propagate (branches A & B)
• resolveActionName failure (Branch A — action deleted between confirmation steps)
• displayName → technical name resolution + fallback
• Multi-record AI selection
• RunStore error propagation (5 scenarios across all branches)
• AI malformed / missing tool call → error outcome
• Default prompt fallback
• Previous steps context in AI messages
• Schema caching (single getCollectionSchema call per collection)
• stepOutcome shape

🤖 Generated with Claude Code

Note

Add TriggerRecordActionStepExecutor with confirmation flow to workflow-executor

• Adds TriggerRecordActionStepExecutor for a new trigger-action step type that selects a record, picks an action via AI, and either executes immediately or persists pendingData for user confirmation before executing.
• Adds LoadRelatedRecordStepExecutor and McpTaskStepExecutor with the same automatic/confirmation branching pattern.
• Introduces RecordTaskStepExecutor as a shared abstract base that standardizes confirmation flow, skipped-state persistence, and buildOutcomeResult for record-task steps.
• Centralizes error handling in BaseStepExecutor: the new concrete execute() wraps doExecute(), catches WorkflowExecutorError to log with cause and return an error outcome, and converts unexpected throws into a generic error outcome.
• Adds SafeAgentPort to wrap all AgentPort calls and normalize non-domain errors into AgentPortError; all executors now use this wrapper.
• Extends the error hierarchy in errors.ts with ~15 new typed errors (e.g. StepPersistenceError, StepStateError, AgentPortError, McpToolInvocationError) each carrying a separate userMessage for end-user display.
• Behavioral Change: AgentPort methods (getRecord, updateRecord, getRelatedData, executeAction) now accept typed query objects instead of positional arguments; all callers and tests updated accordingly.

^{Macroscope summarized 369a398.}

[qltysh]

Coverage Impact

⬆️ Merging this pull request will increase total coverage on feat/prd-219-update-record-step-executor by 0.05%.

Modified Files with Diff Coverage (17)

Rating	File	% Diff	Uncovered Line #s
	...s/workflow-executor/src/executors/read-record-step-executor.ts	100.0%
	...ges/workflow-executor/src/executors/condition-step-executor.ts	100.0%
	packages/workflow-executor/src/executors/base-step-executor.ts	100.0%
	packages/workflow-executor/src/http/executor-http-server.ts	100.0%
	...workflow-executor/src/executors/update-record-step-executor.ts	100.0%
	...ages/workflow-executor/src/adapters/agent-client-agent-port.ts	100.0%
	packages/workflow-executor/src/errors.ts	100.0%
	packages/workflow-executor/src/index.ts	100.0%
	packages/ai-proxy/src/index.ts	100.0%
	packages/workflow-executor/src/executors/safe-agent-port.ts	100.0%
	packages/workflow-executor/src/adapters/console-logger.ts	50.0%	5
	...ages/workflow-executor/src/executors/mcp-task-step-executor.ts	100.0%
	...ow-executor/src/executors/load-related-record-step-executor.ts	99.0%	138
	...orkflow-executor/src/executors/summary/step-summary-builder.ts	100.0%
	...s/workflow-executor/src/executors/record-task-step-executor.ts	100.0%
	...-executor/src/executors/trigger-record-action-step-executor.ts	100.0%
	...ow-executor/src/executors/summary/step-execution-formatters.ts	100.0%
	Total	99.5%

🤖 Increase coverage with AI coding...

In the `feat/trigger-action-step-executor` branch, add test coverage for this new code:

- `packages/workflow-executor/src/adapters/console-logger.ts` -- Line 5
- `packages/workflow-executor/src/executors/load-related-record-step-executor.ts` -- Line 138

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[qltysh]

6 new issues

Tool	Category	Rule	Count
qlty	Structure	Function with high complexity (count = 18): execute	2
qlty	Structure	Deeply nested control flow (level = 4)	2
qlty	Duplication	Found 16 lines of similar code in 2 locations (mass = 92)	2