I know that is a strong statement; but I think what I have written below backs this up.
IMO it would be better to package Gparted as standard in the KDE version of MX.
So I tried installing MX 23.1 KDE and was reminded why I left Mangaro behind...It's sad really; there's a lot I like about it.
While I was in the live session I reached for Gparted, but it wasn't included - instead there was KDE Partition Manager. I had decided that I wanted to delete my swap partition and use a swap file instead; which meant moving boot and expanding root. I had made a snapshot so I wasn't worried; and my data partition was not to be changed - but stupidly I hadn't done a recent backup of it to be safe

Apart from being really fiddly to get it to do what I wanted; once I hit apply it very quickly ground to a halt with a big fat error message; after which the whole SSD was messed up


I should say that I have used Aomei partition manager as well as Gparted and done moves, merges and resized partitions with never a problem.
Several days of data recovery later...

And MX 23.1 generally rocks!
However, for now; I personally think that packaging Gparted in place of KDE Partition Manager would be more in line with the reputation of MX as amongst other things rock solid and reliable. A buggy partition package can do way too much damage both to peoples data and MX's reputation and is why I describe it as a liability.
Apart from appealing to developers to consider this change; I also hope this post will help warn other users and perhaps save them from similar experience as I had.
P.S. I posted elements of this in the AVL respin thread as the question of KDE had come up. I hope I didn't violate any forum rules in doing so; and please feel free to notify me if I should make any changes.
Many thanks.