feat(workflow-executor): deterministic source record for Update Data steps (PRD-777)

[EnkiP]

Part of the deterministic Update Data step work.

fixes PRD-777

What

The update-record (Update Data) step can now resolve its source record deterministically from a build-time-configured stable BPMN step id (selectedRecordStepId), mirroring read-record (Get Data) and trigger-action — instead of always asking the AI to pick among the available records.

Changes

• UpdateRecordStepDefinitionSchema.preRecordedArgs gains selectedRecordStepId (legacy selectedRecordStepIndex kept for back-compat; fieldName/value unchanged).
• update-record-step-executor (handleFirstCall): when selectedRecordStepId is set, resolve via resolveSourceRecordRef (revise-safe; WORKFLOW_START_STEP_ID → base record). Falls back to legacy index / AI selection when unset.
• Server contract (ServerWorkflowTaskUpdateData) + mapper forward preRecordedArgs for update-data.

Tests

• Deterministic resolve skips the select-record AI round; WORKFLOW_START_STEP_ID → base record; unresolvable id → error.
• Mapper forwards preRecordedArgs (selectedRecordStepId + fieldName + value).

Companion PRs: forestadmin-server (orchestrator), forestadmin (editor UI).

🤖 Generated with Claude Code

Note

Add deterministic source record resolution and pre-recorded field/value support to Update Data steps

• Adds selectedRecordStepId to UpdateRecordStepDefinitionSchema and the ServerWorkflowTaskUpdateData interface as a stable alternative to the legacy index-based selectedRecordStepIndex for identifying the source record.
• Extends UpdateRecordStepExecutor.handleFirstCall to support three configurations: both fieldName and value pre-recorded (use directly), only fieldName pre-recorded (ask AI for value via new selectValueForField method), or neither (ask AI for both).
• Adds buildZodSchemaForField/buildZodSchemaForPrimitive forAiTool flag so boolean schemas bound into AI tools are plain z.boolean() (JSON Schema compatible) instead of using z.preprocess string coercion; coercion now happens after tool output.
• Behavioral Change: AI tools now reject string booleans ("true"/"false") directly; coercion to native boolean occurs in the executor after the tool responds.

^{Macroscope summarized 8dad337.}

[linear-code]

PRD-777

[qltysh]

3 new issues

Tool	Category	Rule	Count
qlty	Structure	Function with many returns (count = 6): mapTask	3

[macroscopeapp]

🟡 Medium executors/update-record-step-executor.ts:190

When preRecordedArgs.selectedRecordStepId is an empty string, handleFirstCall treats it as unset and silently falls back to AI/legacy record selection instead of calling resolveSourceRecordRef to resolve the configured ID. An Update Data step can update a different record than its deterministic configuration specifies. The truthiness check should be an explicit !== undefined check, like the load-related executor uses.

Suggested change

	const selectedRecordRef = preRecordedArgs?.selectedRecordStepId
	? await this.resolveSourceRecordRef(preRecordedArgs.selectedRecordStepId)
	const selectedRecordRef = preRecordedArgs?.selectedRecordStepId !== undefined
	? await this.resolveSourceRecordRef(preRecordedArgs.selectedRecordStepId)

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @packages/workflow-executor/src/executors/update-record-step-executor.ts around lines 190-191:

When `preRecordedArgs.selectedRecordStepId` is an empty string, `handleFirstCall` treats it as unset and silently falls back to AI/legacy record selection instead of calling `resolveSourceRecordRef` to resolve the configured ID. An Update Data step can update a different record than its deterministic configuration specifies. The truthiness check should be an explicit `!== undefined` check, like the load-related executor uses.

[qltysh]

Coverage Impact

This PR will not change total coverage.

Modified Files with Diff Coverage (2)

Rating	File	% Diff	Uncovered Line #s
	...workflow-executor/src/executors/update-record-step-executor.ts	100.0%
	packages/workflow-executor/src/adapters/step-definition-mapper.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.