Great! I completely agree that the points outlined are the way forward.
Let's focus on getting the deprecation message into the next release
together with the updated documentation. There are pull requests for these
changes and I would greatly appreciate a review of them.
I'll also modify the existing pull requests to incorporate the idea of a
'legacy' promise type and refer to it the documentation with some
elaboration that in a future version of Keycloak the default will change to
'native' over 'legacy'.
As for the timeline of the changing of the default to 'native' and eventual
removal of 'legacy' what would be the preferred moment to make these