When psbt is created in gui it's now v2 (no option or indication in ui). Using core as wallet software with external signers may result in confusing errors if hw is not compatible with psbt v2. Also multisig users who have bitcoin core nodes on older versions than the node creating psbt will get an "unable to decode PSBT, unsupported version number: unspecified iostream_category error" when attempt to load psbt v2 on any node pre-v32.
I was surprised to see a compatibility break like this so I want to double check that it is intentional
Do users creating unsigned psbt through gui have use case for psbt v2? do we expect this to be more users than will be affected by compatibility break? Is it not be better to continue defaulting to psbt v0 in gui for compatibility, and users who need v2 new features would use cli anyways?