feat: add flow_input to StepTaskRecord and context objects

[jumski]

Add flow_input to StepTaskRecord and expose it in worker context

This PR adds the original flow input to the StepTaskRecord type and exposes it throughout the worker context. This allows dependent steps to access the original flow input parameters, which is useful for maintaining context across multi-step flows.

The changes:

• Add flow_input field to StepTaskRecord in core types
• Expose the flow input in the StepTaskExecution and StepTaskWithMessage interfaces
• Pass the flow input through the task poller to the worker context
• Update test helpers to include flow input in context creation
• Add tests to verify flow input is properly passed through the context

This enhancement enables step implementations to reference the original parameters that started the flow, improving the ability to build steps that depend on initial configuration.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a13db51

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[jumski]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• docs: add note about CONNECT_TIMEOUT fix using jsr:@oscar6echo/postgres fork #562
• fix: reject empty dependsOn arrays and improve flowInput access patterns #561
• feat: make flowInput lazy-loaded to prevent data duplication in map steps #560
• feat: asymmetric handler signatures for simpler flow composition #559
• refactor: simplify step input structure by removing run key and using context.flowInput #558
• refactor: rename input parameters to flowInput and deps for clarity #557
• refactor: change step handler input to use asymmetric pattern for better type safety #556
• feat: add flow_input to StepTaskRecord and context objects #555 👈 (View in Graphite)
• feat: add flow_input field to step_task_record for direct access to original input #554
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit a13db51

Command	Status	Duration	Result
nx run edge-worker:test:integration	✅ Succeeded	3m 49s	View ↗
nx run client:e2e	✅ Succeeded	1m 9s	View ↗
nx run cli:e2e	✅ Succeeded	4s	View ↗
nx affected -t verify-exports --base=origin/mai...	✅ Succeeded	3s	View ↗
nx affected -t build --configuration=production...	✅ Succeeded	4s	View ↗
nx affected -t lint typecheck test --parallel -...	✅ Succeeded	29s	View ↗
nx run edge-worker:e2e	✅ Succeeded	29s	View ↗
nx run core:pgtap	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-12-23 07:55:36 UTC