Thanks to everyone who has contributed to this thread. I just want to respectfully ask if this issue is going to be addressed in an upcoming release—or at least acknowledged as a known regression.
Disabling enable names currently breaks key admin functionality in a way that seems unintended, and the lack of clarity about whether this is by design or a bug is making it difficult for us to plan around. For those of us running production sites where usernames are preferred over full names, this limitation introduces real friction and unexpected behavior.
I understand priorities have to be balanced, but it would be incredibly helpful to get an update from the team about whether this is on the radar. Thanks in advance for any insight you can provide.