I'm not saying it's not reasonable, I'm saying that if applications don't care (especially closed source ones which don't care about being good citizen) and they recreate their surfaces when they don't need to, it's not really up to Wine to mitigate that. IMO the WSI should be aware of such issues and take them into consideration in their design, regardless of what is reasonable or possible by spec.
That is true. However, if an app doesn't work on the platform it is meant to work on would cause the app developer to fix the bug on their side. The Wayland WSI works in a way that is legal by the Vulkan spec; Windows also works in a legal way. But there are a few handful of windows apps that don't work on wayland, and IMO that is Wine's job to correct since it translates the windows interpretation of these specs to the host system. Regardless, this bug is very difficult to trigger "accidentally" on a native app; you need to create a new wl_surface, VkSurface, and swapchain for every suboptimal. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11342#note_145152