@JamesPetty, thanks for confirming this, although this is not the response I hoped for.
I can see in my EAP-enabled site that the hide locked filter is working now, yes.
What I don’t yet see is that locked fields can be added or removed to a field configuration. I guess that is still to come, even in an EAP-enabled site?
Fyi, as a consequence of this constraint to customfields, we are considering moving away from a Forge customfield and instead implementing an Automation Action. Our app’s main use-case is with Automation anyway.