feat(cloudflare): expand workflows api

[Gerbuuun]

Expand the Effect-native Cloudflare Workflow wrapper to cover the current Workers API surface with an object-based step API.

const result = yield* Cloudflare.task({
  name: "call-api",
  retries: { limit: 3, delay: "5 seconds", backoff: "linear" },
  effect: Effect.gen(function* () {
    const context = yield* Cloudflare.WorkflowStepContext;
    return { attempt: context.attempt };
  }),
  rollback: ({ output }) =>
    output ? cleanup(output.id) : Effect.void,
});

const instance = yield* workflow.create({
  id: "order-abc",
  params: { orderId: "abc" },
});

const approval = yield* Cloudflare.waitForEvent("approval", {
  type: "approval",
  timeout: "1 day",
});

yield* instance.sendEvent({
  type: "approval",
  payload: { approved: true },
});

• Add step config, step context, rollback, and waitForEvent support
• Add create options, createBatch, restart, sendEvent, rollback status, and extended event metadata
• Update Workflow docs generation to pick the resource JSDoc instead of earlier helper class comments

[sam-goodwin]

I think it wouldn't be better if the id was the first argument instead of an object property to align with the rest of alchemy's api design.

[john-royal]

Done — reshaped to id-first so the name leads and the Effect stays positional, with retries/timeout/rollback in an optional third config object:

yield* Cloudflare.task("process-order", Effect.succeed({ orderId: "abc" }));

yield* Cloudflare.task("call-api", effect, {
  retries: { limit: 3, delay: "5 seconds", backoff: "linear" },
  rollback: ({ output }) => output ? cleanup(output.id) : Effect.void,
});

This keeps the simple task(name, effect) call working unchanged.

[sam-goodwin]

Should we support an Effect schema here?

[john-royal]

Deferring this for now to keep the PR focused — waitForEvent (and task/create) stay on the unchecked <T> generic in this change. Adding optional Effect Schema decoding for event payloads is a good follow-up and can land separately.

[just-be-dev]

These could just be defined inline. It's how they do it.

    export abstract class WorkflowStep {
        do<T extends Rpc.Serializable<T>>(name: string, callback: (ctx: WorkflowStepContext) => Promise<T>, rollbackOptions?: WorkflowStepRollbackOptions<T>): Promise<T>;
        do<T extends Rpc.Serializable<T>>(name: string, config: WorkflowStepConfig, callback: (ctx: WorkflowStepContext) => Promise<T>, rollbackOptions?: WorkflowStepRollbackOptions<T>): Promise<T>;
        sleep: (name: string, duration: WorkflowSleepDuration) => Promise<void>;
        sleepUntil: (name: string, timestamp: Date | number) => Promise<void>;
        waitForEvent<T extends Rpc.Serializable<T>>(name: string, options: {
            type: string;
            timeout?: WorkflowTimeoutDuration | number;
        }): Promise<WorkflowStepEvent<T>>;
    }

I do need this though, so thank you for putting up the PR!

[just-be-dev]

Ahh, nvm, I see why you separated it out.

[Gerbuuun]

Thanks for the feedback. I'm in the middle of exam week so it'll be probably end of next week I'll continue working on this