ext_image_copy_capture_session_v1 format constraint changes are poorly defined

The protocol does not say what the contents of a ext_image_copy_capture_session_v1.done sequence are. Does the compositor have to send all constraints whenever any constraints change? If not, how does the client distinguish between only the size changing and no longer any formats being available? Sending the dmabuf formats every time is not reasonable due to the large amount of data.

Currently I see no reasonable way to handle this except by stopping sessions whenever any format constraints change.