This is generally a problem in various forms at firms of all sizes, so running away is simply conceding that you lack the desire to develop some of the most important skills required when moving into an elevated lead or management position: the ability to compel people without forcing them and the ability to compromise.

Looking at your list of gripes, some are clearly critical issues (ie. Automated production monitoring and alerting of customer facing system) while some are obviously nitpicking (ie. Comments and documentation? Lol). Drop the "nice to have" stuff and instead pursue the "need to have" items. No CEO worth his salt is going to accept the liability of customer loss or lawsuit simply because no one thought to build some simple monitoring jobs. At the same time, I cringe at the prospect of a developer even mentioning comments or version control minutae to an executive level - definitely NOT a point to be explicitly bright up beyond some quantified metric on a regular report. It's distracting noise for him and definitely your problem to solve. Given that you mentioned being very well compensated, well that's a pretty good hint that the task ahead of you will be challenging and often not in the way you expect, as evidenced by this case.

On that note, be sure all these things are actually important for that specific business. I once worked on an in-house, Windows based C++ trading system with over 600k lines of code and there wasn't a single unit test to speak of. Granted, it was developed following SDLC and included 4 levels of testing (dev integration, ba functional, user demo and qa) but the system was running continuously for almost a decade and reaped profits in the high 9 figures. Some shops produce high quality software with deeply knowledgeable long tenured senior technologists and don't necessarily require such testing frameworks as they perform that task themselves and often far better than some pre-canned block of code ever will. I've also been in shops where testing and coverage minimums were required and tracked precisely in real time, preventing code release if standards were not met. The end result were loads of trivially passing, nonsense tests and a culture where developers often felt compelled to create even those for only the lowest hanging fruit to meet the minimum requirements for a deadline or risk a monetary impact to their bottom line. So don't just rotely follow (let alone impose) paradigms without realizing that quantifying their value is hard in many scenarios, not to mention could be construed as stepping on toes...

As some have mentioned, the best managers are those who are able to gain the trust of their teams and this is something that takes time and strings of successes along the way. At the same time, lead by example and instead of imposing your will, let the results speak for themselves. Add tests in some minor modules and if they fail, use the opportunity to demonstrate how they saved potential headaches or worse. I've found that people invariably flock to those who demonstrate not only ability and intelligence, but also civility and geniality. I can't even begin to explain how small humorous exchanges have vastly strengthened my network. I've had to lead teams of juniors and offshore folks without any official management title and its forced me to adapt and develop various methods of building repoir and ultimately compelling people to get things done, with few sour grapes to speak of and many successes (and comp increases) along the way.

Regardless of all of the above, you're still getting paid, right? By your admission, paid WELL. So why would you leave that because you believe you're not being allowed to do your job (most of which actually requires more work and maintenance)... 2 weeks in?!? Perhaps after 6-12 months, you come to the conclusion that the culture is just not for you. So, leave then - I assure you there will be just as many, if not more opportunities then, except at that point you can be confident you've shed any insecurities and gave it your best shot and have some quirky behavior tolerance to boot. That sort of techno "battle scar" is quite visible as a sort of confidence backed by wisdom and experience and makes prospective employers wet their pants. Or maybe you just kick ass and prove you're worth every penny - smiling all the way to the bank. Either alternative is far more appealing than tucking your tail and running. Food for thought