feat(workflow-executor): type-specific PATCH body validation

[Scra3]

Summary

• Adds per-step-type Zod schemas for PATCH /runs/:runId/steps/:stepIndex/pending-data body validation
• Adds relatedCollectionName to FieldSchema type
• Addresses PR review gaps (additional test coverage, fixture cleanups)
• Uses StepExecutionData cast instead of Parameters utility type

PR 2/3 of the pending-data refactor chain. Depends on #1507.

Test plan

• Validation tests for each step type (update-record, trigger-action, mcp-task, load-related-record)
• Unknown/extra field rejection tests
• yarn workspace @forestadmin/workflow-executor test passes
• yarn workspace @forestadmin/workflow-executor lint clean

🤖 Generated with Claude Code

Note

Add type-specific Zod validation to the PATCH pending-data endpoint

• Adds pending-data-validators.ts with strict per-step Zod schemas for update-record, trigger-action, mcp-task, and load-related-record step types.
• The PATCH /runs/:runId/steps/:stepIndex/pending-data handler in executor-http-server.ts now looks up the step type, selects the matching schema, and returns 400 on validation failure or 404 for unsupported step types.
• LoadRelatedRecordStepExecutor no longer persists relatedCollectionName in pendingData; instead, it re-derives it from the current collection schema at confirmation time, and fails with an error outcome if the field cannot be resolved.
• Behavioral Change: PATCH requests with unknown fields or invalid types are now rejected; relatedCollectionName is no longer accepted or stored in load-related-record pending data.

^{Macroscope summarized 5091231.}

[qltysh]

Coverage Impact

Unable to calculate total coverage change because base branch coverage was not found.

Modified Files with Diff Coverage (3)

Rating	File	% Diff	Uncovered Line #s
	...ow-executor/src/executors/load-related-record-step-executor.ts	100.0%
	packages/workflow-executor/src/http/pending-data-validators.ts	100.0%
	packages/workflow-executor/src/http/executor-http-server.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.

[qltysh]

All good ✅