OSM Inspector throws a warning about this relation. I find my solution just fine. Here's more information about these cases (https://josm.openstreetmap.de/ticket/18861). If anyone thinks this should be mapped differently, don't bother asking for my opinion, go ahead and fix it.

Yes, I noticed yesterday. I fixed them all, I think. I also updated JOSM. Let's see what happens.

I do not know if this is the right communication channel for this, but I will use it anyway.

JOSM (v 17919) did not detect these errors as far as I can remember. The validation tool did work for other errors like empty roles and untagged ways. Nevertheless, I have been improving my procedures to avoid this to happen. AAMOF, most of these errors are older edits, and I have been uploading hundreds of postal codes almost daily.

Thanks for the heads-up. Have a nice day.

Yes, I am using JOSM, and I am aware of some issues I try to fix immediately, but of course this amount of changes will cause problems that I am probably not aware. I appreciate your report all the same. I will try to figure it out with the tool you present.

Con relación al error de JOSM mencionado en el comentario del changeset, se refería a una etiquetación errónea del municipio vecino Huixquilucan, que había sido desprovisto de una keytag type=boundary. Este error ya fue subsanado.

Quise decir meses, no años.

I fixed the bad keys/values. It was a distraction on my side, I'm sorry. Once again, thank you mueschel.

I'm on it. Thanks.

Espero que lo hayas hecho, al parecer el problema está resuelto (yo mismo ya lo he verificado) en los datos pero el renderizado sigue siendo incorrecto en todos los niveles de zoom.