Add fatal step e2e test

[pranaygp]

Just adding a new e2e test for the fix in #322.

Didn't add it to that PR directly because this e2e test will likely fail in different places for different reasons and it shouldn't block #322 for an immediate fix

[changeset-bot]

⚠️ No Changeset found

Latest commit: b9218f0

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
example-nextjs-workflow-turbopack	Ready	Preview	Comment	Nov 13, 2025 4:07am
example-nextjs-workflow-webpack	Ready	Preview	Comment	Nov 13, 2025 4:07am
example-workflow	Ready	Preview	Comment	Nov 13, 2025 4:07am
workbench-hono-workflow	Ready	Preview	Comment	Nov 13, 2025 4:07am
workbench-nitro-workflow	Ready	Preview	Comment	Nov 13, 2025 4:07am
workbench-nuxt-workflow	Ready	Preview	Comment	Nov 13, 2025 4:07am
workbench-sveltekit-workflow	Ready	Preview	Comment	Nov 13, 2025 4:07am
workbench-vite-workflow	Ready	Preview	Comment	Nov 13, 2025 4:07am
workflow-docs	Ready	Preview	Comment	Nov 13, 2025 4:07am

[pranaygp]

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

• Add fatal step e2e test #324 👈 (View in Graphite)
• Fix workflow failing because of function timeouts #322
• main

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

[VaguelySerious]

Looks like this works in prod but the output shape is just slightly off?

---

And then it fails in local generally presumably because killing the process will kill more than just the API handler, since it's all running the same process?