Often there's a great use case for two things to work together but you have a chicken and egg situation. You need a top-down edict to get everyone on the same page.
Wrong. Take the LSP example: a) I don't have time to add LSP support to Vim, Emacs, KDevelop, etc. and write language servers for Python ok n, C++, Rust, Go, etc. and b) those projects would not accept my contribution if I tried. They would say "what is this LSP thing that nobody uses? Come back when it's popular".
The latter is where you need the coordination. In a company someone high up can say "we're doing it's like this" and everyone has to fall in line.
In a company, yeah. LSP is a Microsoft initiative. Swap your open source examples to proprietary editors from different vendors and it's otherwise the same story, but now you can't provide both the chicken and the egg yourself.