[enhancement]: workflow json fields should be in stable order

[keturn]

Is there an existing issue for this?

• I have searched the existing issues

What should this feature add?

When I save my workflows to file, I'd like to avoid the extraneous diff noise that comes from the fields moving around. i.e. "version" might come first once, but "type" on a later re-save.

There should be some sort of canonical order to these, whether that's alphabetical or the order of the pydantic fields or whatever.

[example workflow diff]

[psychedelicious]

The ECMAScript spec makes no guarantees about the ordering of keys in plain objects, though most implementations do not change the order once set. Not sure about python.

There are a number of places where workflows are written to JSON, in the frontend and backend, so any change would need to be implemented in JS and python, in each place.

[keturn]

There's RFC 8785 Canonical JSON with various implementations. But that canonical form strips all whitespace, making it ill-suited to line-oriented version control.

Maybe what I'll end up doing is running workflows through jq --sort-keys before committing them.