"Second system syndrome" is what came to my mind. But I'm wicked old.

Actually its not going to be that.

That's when you've got something small that works and the rewrite is a bloated mess of every feature you could dream of.

This is the case where you've got an accumulation of over a decade of technical debt and Chesterton's Fences and someone who has no idea why the code is the way that it is inherits it and decides to rewrite it, and not knowing which constraints are necessary and which aren't they throw away most of them and find out the hard way that the problem isn't actually that simple.

It is almost the inverse of the second system syndrome.

But it is abundantly clear that Elon doesn't even know how to have this conversation.

In a sane acquisition a list of issues would have some out in technical dd. Not that Elon would have listened to anyone doing technical dd.