fix(workflow-executor): always log WorkflowExecutorError message, even without cause

[Scra3]

Summary

• WorkflowExecutorError thrown without a cause (e.g. Zod validation failure on pendingData) was silently swallowed — no log on the executor side
• Now always logs error.message; cause and stack are appended when present

Test plan

• base-step-executor.test.ts updated: verifies logger.error is called with the error message even when no cause is set
• 791 tests passing

fixes PRD-214

🤖 Generated with Claude Code

Note

Fix BaseStepExecutor to always log WorkflowExecutorError message even without a cause

Previously, WorkflowExecutorError instances without a cause were silently swallowed — no error log was emitted. The fix removes the conditional guard in base-step-executor.ts so logger.error is always called with error.message. When a cause is present, logging behavior is unchanged (message, cause, stack).

^{Macroscope summarized 347f1f2.}

[linear]

PRD-214

[qltysh]

2 new issues

Tool	Category	Rule	Count
qlty	Structure	Function with many returns (count = 5): execute	1
qlty	Structure	Function with high complexity (count = 11): execute	1

[qltysh]

Coverage Impact

This PR will not change total coverage.

Modified Files with Diff Coverage (1)

Rating	File	% Diff	Uncovered Line #s
	packages/workflow-executor/src/executors/base-step-executor.ts	100.0%
	Total	100.0%

🚦 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.