You might want to exclude certain parts here, the downside would be otherwise that any ... const/func would autofix to use statement:

use const JSON_ERROR_NONE;

and we didn't decide yet to spam the use block with also constants, functions and CO :)
For now this should probably be limited to class/interface/trait references only.

It also blindly converts e.g.

// @see \...\TransferToEntityMapper::mapEntity()

into a use statement, also killing the original docblock..
which is just bonkers, that's a docblock and shouldn't be touched.
So I guess it has some small bugs that also need solving first.

I opened up a ticket for now slevomat/coding-standard#1265
But I would be careful with adding this one, as it can also effect projects or plugin code

I didn't see that happen in any of the type changes I made, but there's no rush while your issue is resolved.

Looks like the slevomat bug was patched. Is this ok now?

Don't want things like use const JSON_ERROR_NONE;.

Don't want things like use const JSON_ERROR_NONE;.

I believe that can be disabled with allowFallbackGlobalConstants