I can see where @invisnet is coming from here. I have noted two sorts of commitment to CP from WP plugin developers. Which means I already mentally divide WP plugins into three groups.
The first is like Paul with Shield - he said right from the start he was fully in and would support CP and has made changes to his code to accommodate us (eg in the file checking to avoid warnings).
The second group is like the dev of the Stripe plugin I am using on my CC sites. He said: “Hmmm, well I can’t see any reason why it shouldn’t work and will give conditional support for now”.
The third (and largest) are those that work with 4.9 and so work with CP but the plugin devs probably have no idea CP even exists.
To me, Paul’s approach inspires confidence and I feel good about using his plugin. The second ones make me nervous and I feel like I will need to keep a close watch on how it goes. It could break with any update. Same with the third group.
But, are we saying that all of these plugins get lumped into the “Works with” section? That doesn’t seem fair on Paul, and others like him.
To me the solution is quite simple - keep the two sections but make the first one something like “Developed for CP or fully supported for CP”. That is where I would always be looking first for a plugin to use… if I can’t find something there, then I would move (reluctantly) onto the other section.