2.0 - start of discussion/ideas/breaking changes #410
Description
In our last meeting (11/26/2025) we went back and forth on some items that could potentially be breaking changes. We decided not to put that in 1.1.0 and thought now would be a good time to start discussing items for a 2.0 release. This is VERY early days. We're not looking to rush a 2.0 out as tooling is just ramping up for 1.0 and with the addition of async api support in 1.1.0 soon we'll let that percolate for some time. However, there are a few things we'd like to see added in the not too distant future that would likely result in breaking changes. Hence.. 2.0 discussion.
We can use this thread to start off on that path.
The item we decided to push off was the 'kind' discriminator in each step. For now it's possible to utilize the sourceDescriptions 'type' field to identify/validate a given step's kind/type. We have been discussing the addition of human in the loop and mcp types, as well as possibly some sort of transformation type or function type perhaps. Presently you would need to use API calls to achieve this and certain workflows we've discussed get a bit unwieldy with the conditional GOTOs.
Feel free to add more to this thread with ideas that might enhance Arazzo as well as potentially be breaking changes that would go in a 2.0.0 release.