PIPs? RTO? You work for amazon, right?
If you want to work remotely and your director wants people back in the office then they’d probably want to get rid of you rather than having a remote worker other people could point to and say “but he works remotely, why can’t I?”. If that’s the case then your manager could have put you on a PIP so you’d come under unregretted attrition rather than regretted attrition.
Managers can get judged on how many of their reports leave the company/team and if the company wants them to stay or not. If the manager can get rid of someone on a PIP then that looks good for the manager. Maybe this is what’s happened to you in this case.
Anything to do with naming is going to be doomed to bike shedding (https://en.wikipedia.org/wiki/Law_of_triviality). The only way to avoid the kind of problem you mention is to have one person come up with all the naming rules and to enforce it.
You’re right to think it’s important because it’ll make maintenance significantly easier than having 3-4 disparate naming schemes. However, there’s no way that you can get a group of people to agree on a single naming scheme. Everyone will have their own idea which will make complete sense to them but to no one else, and they’ll argue for hours about this. There’s no easy solution, even though it should be trivial.