Any time we went through the certification process it was just making sure that expected functionality was in place. A lot of it revolves around platform interaction and overall functionality.
Regarding expected warnings, screens, etc. As long as they're present and remain onscreen long enough to be read, that's all that really matters. But that's a stretch cause sometimes it's so fast you can't even read the whole thing and it still works, lol.
My understanding was that the process has never changed really. The only things that get adjusted revolve around the platform and operating system itself. Along with any kind of new tech. But if it's all the same you just kind of replace the name with something else and move on, lol.
A lot of people don't realize that bugs have no affect on this process unless they're crucial A bugs that don't allow the game to be played whatsoever. As long as the game can boot, run, soak, and shutdown properly that's all that really matters to them.
The overall quality of the game in terms of bugs and otherwise is really on the developer and publisher. Which, usually isn't an issue because both want to be proud of the project that they've worked on and are submitting to cert.
CP:2077 is clearly a different beast through and through.