* feat: add waitForResult parameter to invoke

* fix: return types

* fix: pass workflow to context.call

* fix: fmt

* fix: flaky invoke test

test was checking the result of context.notify in a loop, which resulted in different number of calls. fixed it by waiting for a long while and notifying once.

* fix: timeout issues in test

* ci: fix wrangler deploy

* fix: review

* fix: refactor step submissions

* fix: bump ai dependencies and fix tests

* fix: refactor getHeaders method

* fix: tests

* fix: remove comment

* fix: fmt

* ci: fix wrangler publish

* feat: fix callback-failurecallback headers

handles https://linear.app/upstash/issue/DX-1718/workflow-js-fix-fromcallback-headers

* fix: tests

* fix: review

* fix: rm unused invokeWorkflow

* fix: test

* fix: express dependency

we were getting type errors after @types/express v5.0.1 was released a week ago. Pinning the version of this package in the workflow-js and examples/express to 5.0.0 fixed the issue. But this wasn't a good solution in the long term.

another solution was removing the dependency from examples/express and keeping it in workflow-js. We don't import anything from @types/express but we still need it in our dependencies.

* fix: add debug logs

It looks like context.env is only defined in Cloudflare Workers. https://hono.dev/docs/api/context#env

When the serve method from hono is used in vercel, context.env is undefined which causes an error.

Fixed the issue by checking if context.env is defined and falling back to process.env if it isn't.

Fixes: #91

* fix: only allow string step names

* fix: lint

* fix: use warn instead of throwing in non-string step name

…ond (#101)

* feat: add flow control

* fix: tests

* fix: fmt

* fix: mock qstash methods of client in test