[types] Add more to Workflow step context

[pombosilva]

No description provided.

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR adds step (name + count) and config fields to WorkflowStepContext.

1. [MEDIUM] config should likely be optional. The WorkflowStep.do() has an overload that takes no config argument. If a user calls that overload, will config always be populated in the context (e.g., with defaults), or will it be undefined? If there's any chance it's not always present, the type should be optional to avoid runtime surprises.
2. [LOW] Generated snapshots need regeneration. The types/generated-snapshot/ files still show the old WorkflowStepContext shape (only attempt). CI will likely fail on the snapshot diff check. Run just generate-types (or equivalent) and include the updated snapshots.

---

This review was written by an AI assistant and may contain inaccuracies.

[ask-bonk]

Review posted on PR #6523. Two findings:

1. [MEDIUM] config on WorkflowStepContext should likely be optional (config?) since do() has an overload that takes no config argument — if the runtime doesn't always populate it, users trusting the required type will hit runtime errors. Posted as an inline suggestion.

2. [LOW] The generated snapshots in types/generated-snapshot/ still have the old shape and will need regeneration to pass CI.

github run

[github-actions]

The generated output of @cloudflare/workers-types matches the snapshot in types/generated-snapshot 🎉