But you have no real architecture details, only a small number of bullet points on how it's supposed to behave and a simple but not horribly descriptive API. That isn't an architecture, that's just marketing materials.
They are completely irrelevant to anything.
Given only that, you cannot possibly make informed commentary on how it will behave in practice, you are just parroting a story.
In particular, you said "it let poorly-behaved apps drain significant amounts of battery in the background and it's not true that Apple has now added that possibility."
You cannot possibly assert this with any real details to back it up, because you do not know how this architecture operates past "apple says they won't be woken up enough or run long enough to drain battery". If you have the actual details necessary to back this statement up, please add them.
Unless you are talking at such an abstract level where everything that matters is an implementation detail, in which case it's very easy to design perfect architectures that have no problems!
We don't believe people when they make crazy claims about crypto, without seeing the actual details and implementations.
We should not trust Apple or Google's marketing points about their architectures when trying to make "architectural criticism".
In the end, if you really believe "architectural criticism" is possible without actual detailed design info, carry on.
But to me, that's a worthless discussion based on what are essentially talking points.
In any case, all that matters in the end is performance in the field, so this entire discussion is mostly technical masturbation until real users have phones in hands.