How does configuring the optional mgmt API change operation of the controller?

This OpenZiti article says this ReDoc HTML reference is the mgmt API spec for my Ziti controller, but it appears to have many of the same REST endpoints / API operations as are defined in the edge-client swagger, so I’m not sure what is the separation between edge-client and mgmt when both are enabled.

I think this means that ziti-controller provides the functions of both mgmt and edge-client via the edge-client server listener when mgmt.listener is undefined, but it’s not yet clear which operations, if any, become unavailable in edge-client API when mgmt.listener is defined.

Edward sent me this link to the controller’s changelog and it answers my question completely. Thank you!