I am sorry to hear you had such an issue, but it is great that you found a solution. You are correct, this behavior is unexpected, we will verify what you wrote and fix our documentation as needed.
Unfortunately, as far as I remember, this is something related to how MongoDB works with GeoPoint queries, it is not something we designed on purpose.
And, of course, you are right, it is not 1967. This behavior probably dates a few years back to when we first implemented the GeoPoint functionality. As a matter of fact, you might remember it, as back then you were still part of our team :)