What's insane here? Waking the machine up is a legitimate use case, and it's easily traceable and configurable.
And easily configurable is subjective. Sure most readers here can work through it but requiring use of the CLI is not "easy" for most people. Not to mention the discoverability of that feature in the first place.
I am the user. I use the machine, not the other way around.
The fact that such a subsystem exists isn't an indication of malice or a subversion of your will. There will be bugs in such a system, but the system still needs to be there.
Because that is the usecase that hibernate is for. It makes laptops convenient by allowing you to just close the lid, put it in a bag, go somewhere, take it out of the bag, and then open it and continue working. If you need to tell people that they need to shut down their computers properly before putting them into bags, you have just produced a vastly inferior product.
This is an area where Microsoft desperately needs a Chief-making-it-not-suck-Officer. Someone who can just take that surface laptop, notice that some idiot actually wrote that you are supposed to shut it down instead of hibernating to put it in a bag, and yell at people until the product is fixed. Because right now it's broken.
Pre-covid I had many co-workers who would sit down, plug their laptop into the dock, and work the whole day without ever opening the lid.
I've also spent 15+ years with a laptop connected to my TV that never has the lid open, and I definitely expect it to wake up when I sit on the couch and wiggle the Bluetooth mouse.
And running a configuration command is in fact you telling it what to do.
So the actual issue is open-systems vs walled-gardens in system design and how it surfaces in consumer products. The only thing Windows can do is force you to review each and every device driver on install for e.g. can wake machine. A non-starter for a consumer OS.