v2.5.3

WorkflowRunOutput now exposes a files field and uses consistent JSON (de)serialization. This fixes prior serialization errors and makes file artifacts first-class, enabling teams to programmatically consume outputs and chain file-based steps across workflows.

Details

• Files returned directly in API responses for simpler integration
• Consistent serialization eliminates client-side errors and custom plumbing
• No migration required

See Cookbook for reference