Is reading the spec officially dead in the era of vibe coding? 🧐

Honest question for the senior devs here.
Are we still forcing developers to read the official documentation, or has the industry accepted that typing prompt after prompt and "vibing" through compiler errors is the new normal?
I just spent three hours fixing a production bug that could have been avoided by a 5-minute look at the spec. Yet, half of the team thinks that reading documentation is a waste of time now.
How do you enforce reading the specs without looking like an outdated micromanager?
P.S. Put my current stance on this whole "vibe vs spec" drama directly in my bio. It's the only way I can express my frustration today.