That's my experience, I framed houses for a few years after college and the architects thought they were gifts from God. Engineers were mostly cool, though. Most of them would understand "Your design is dumb and here's why. We're gonna have to change it" and they'd usually learn from it.
My best day on a job site was watching the architect wearing zero safety gear walk right into a temporary support for a wall. It was fantastic.
Very early on in my career in consulting engineering, I had an architect tee-off on me for changing the ceiling heights of the office space she'd designed.
I'm electrical, all I was concerned with was circuiting her lights, that was it. I had documentation showing that I'd worked off of exactly the same ceiling heights she had sent me. Heights that she'd apparently changed somewhere along the line without informing the client, who was an international conglomerate, and notoriously picky to work for.
That could have blown over, had she not berated me over email while CCing the client, my management and just about anyone else involved with the project. I made sure to "reply all" showing where the change had happened. She was replaced on the project the following week.
After that I stuck to industrial projects, where the buildings were non-descript concrete and steel boxes with no architectural involvement.
In my experience the story doesn't end with them being fired it ends with them yelling at me for not anticipating what they wanted, getting backcharges because why not, and years of fights inside and outside of work.
But hey why shouldn't we all just do our work professionally and go home?
Generally firing an architect midway through a project means the project is dead, particularly since they control the permitting and if they are the arch of record they have their stamp on it. Wonder how that went.