feat(types): add workflow rollback types (withRollback, rollbackAll, TerminateOptions)

[dmmulroy]

Summary

Adds TypeScript type definitions for the Workflows saga rollback API and terminate options.

Note: Depends on internal gitlab workflows!750 which adds the underlying engine support.

Changed Files

• types/defines/rpc.d.ts - added RollbackHandler<T>, RollbackStepConfig, RollbackAllOptions, and withRollback/rollbackAll methods
• types/defines/workflows.d.ts - added rollingBack status, TerminateOptions, updated terminate() signature

Types Added

// rpc.d.ts
export type RollbackHandler<T> = {
  do: () => Promise<T>;
  undo: (err: unknown, value: T) => Promise<void>;
};

export type RollbackStepConfig = WorkflowStepConfig & {
  undoConfig?: WorkflowStepConfig;
};

export type RollbackAllOptions = {
  continueOnError?: boolean;
};

// Added to WorkflowStep class:
withRollback<T>(name: string, handler: RollbackHandler<T>, config?: RollbackStepConfig): Promise<T>;
rollbackAll(error?: unknown, options?: RollbackAllOptions): Promise<void>;

// workflows.d.ts
type TerminateOptions = {
  rollback?: boolean;
};

// InstanceStatus.status now includes 'rollingBack'
// WorkflowInstance.terminate(options?: TerminateOptions)

Snapshot Regeneration Needed

The check-snapshot CI job fails because type snapshots need to be regenerated. Running just generate-types on macOS causes a segfault.

Could a maintainer with Linux access help regenerate the snapshots?

---

Note

This PR was written with AI assistance.

[codspeed-hq]

Merging this PR will not alter performance

Summary

✅ 129 untouched benchmarks
⏩ 49 skipped benchmarks¹

---

_{Comparing dmmulroy:dmmulroy/workflows-python-rollback-api (28aacc0) with main (613091c)}

Footnotes

1. 49 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[danlapid]

If this is a new feature then ideally we should add support for JS Workflows at the same time as Python Workflows.

though admittedly I don’t know if it is or not so feel free to educate me.

[Caio-Nogueira]

Seems like we're duplicating the engine logic for this feature. Would it be possible to call into withRollback and rollbackAll from the workflow engine and avoid leaking internals? Seems like a cleaner approach. Although we would probably need to figure out type translations between js errors and python exceptions...