feat(workflow-executor): align datasource activity-log labels with the browser engine [PRD-449]

[nbouliol]

What

Aligns the datasource activity-log labels emitted by the workflow-executor with the legacy browser engine (ISO), fixing a production audit-trail crash on label-less entries.

fixes PRD-449

Context

Since the activity-log refactor (PRD-442), logs are emitted per datasource call in AgentWithLog.audit(), not per step. This dissolves the original dynamic-label problem (the name is now known at the call site, after AI resolution) — no executor or base-class refactor needed. The fix is just injecting the ISO label into each audit target.

Changes (agent-with-log.ts)

Operation	Label	Source
update	updated	static
action	triggered the action "<technical name>"	query.action
listRelatedData	list relation "<displayName>"	resolved from source schema, falls back to technical name
index (read)	none	ISO; getRecord is shared across step types, a blanket label would mislabel update/trigger/load reads

• resolveCollectionId -> resolveSchema (returns the full CollectionSchema) so the relation displayName can be looked up.
• action label only fires in FullyAutomated mode (preserved naturally: executeAction is only called in that branch; otherwise the front executes and logs).

Tests

• agent-with-log.test.ts: exact-label assertions for update / action / relation displayName + technical-name fallback.
• Updated existing createPending assertions in update / trigger / load-related executor tests.

Validation

• yarn workspace @forestadmin/workflow-executor test -> 925/925
• yarn workspace @forestadmin/workflow-executor lint -> 0 errors
• yarn workspace @forestadmin/workflow-executor build -> ok

Out of scope

• MCP executor (already labelled)
• The N-logs-per-step behavior of load-related (pre-existing since PRD-442)
• Rich \"...in workflow Y\" labels (requires orchestrator contract change)

🤖 Generated with Claude Code

Note

Align datasource activity-log labels in workflow executor with the browser engine

• Adds human-readable labels to activity log entries in AgentWithLog: relation reads use 'list relation "<displayName>"' (falling back to the technical name), record updates use 'updated', and action triggers use 'triggered the action "<action>"'.
• Replaces the resolveCollectionId helper with resolveSchema, which fetches and caches the full CollectionSchema to support label computation from field display names.
• Adds a relationLabel helper that looks up the matching field's displayName in the schema, falling back to the technical relation name.
• Updates integration tests across agent-with-log.test.ts, load-related-record-step-executor.test.ts, trigger-record-action-step-executor.test.ts, and update-record-step-executor.test.ts to assert the new labels.

🖇️ Linked Issues

Addresses PRD-449.

^{Macroscope summarized 4fb6032.}

[linear-code]

PRD-449

[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/agent-with-log.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.