I didn't say "it failed because it didn't do X". They said "... failed to gain developer adoption ....". To that specific point, I contend there is a clear and direct causal link between the decisions they made, and that lack of adoption. Of course I can't prove that in the strictest sense, but it's not hard to see that a lot of (potential) G+ developers kept asking and asking and asking for usable APIs and never got them. Speaking only for myself, as somebody who was initially a G+ fan and might have been inclined to build things on top of G+, I never did so for exactly this reason. Yes,"n=1" and all that, but a lot of other devs were very public with their position on this as well.
Obviously their decision to close it down involved multiple factors, but the lack of developer adoption was specifically called out by Google as one of those factors.
Google+ came out, if you'll remember, at the time that Page became CEO again and pivoted the company's direction away from standards and more towards product. In the case of social that clearly failed. In the case of Android it did not.
It would be fun to spend some time doing a more detailed analysis of the whole thing, including all of that historical context, but I don't have the time right now.
It was a catastrophic misjudgement that killed the platform at birth.
It's clear that it failed. It's less clear that the reason is necessarily any of the ones you gave. Every dominant social network has been a walled garden, and, contrariwise, every attempt to create a major social network based around federation and open standards has, so far, failed.
Don't get me wrong, I'd love to see one succeed, and who knows, maybe Mastodon will overtake Facebook one day, but I don't see any evidence in the Google+ shutdown that suggests that this is the case.