If you want to read the real discussion, go here.
The short version is that was a programming error during the global coverage project. The reason for the bug has been identified, but it cannot be easily fixed without reprocessing every single boundary globally, so it can’t really be set up as a single task.
It will be fixed when the OpenStreetMap update process is rolled out, but that implementation is still being developed (and has probably taken a back seat right now to figuring out sync backlog issues)