This affects nearly every street that straddles a city border. There are way too many to handle these manually so there isn’t much point in reporting them…
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)
I’m very new here, so don’t have much historical knowledge.
I don’t really see it as a big deal, as I’ll most likely get to all those nodes anyway.
I’ve finally run enough, with nodes in mind, that I think I’m getting more efficient, and realized I don’t have to finish a street today, knowing I will run past it tomorrow.