spec: per-geolocation-ubigeo-postal-code

[kaio-donadelli]

What is the purpose of this pull request?

Define how Peru geolocation must always resolve INEI ubigeos and never leak Google's 5-digit CPN into checkout addresses (LOC-21884 / Zendesk #1290373).

Summary

• Spec keeps 6-digit ubigeo as the canonical Peru "postal code" (guidance from CXs)
• Stops mapping Google postal_code; derives ubigeo from department/province/district with prefix/accent-tolerant matching
• Includes refreshing Peru country data from INEI 2025; out of scope: switching to CPN, tightening regex to /^\d{6}$/

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[sonar-workflows]

Quality Gate failed

• 7 New Issues (is greater than 0)
• 0.00% Coverage on New Code (is less than 75.00%)

Project ID: address-form

View in SonarQube

[kaio-donadelli]

Superseded: the SDD now lives in the implementation PR #707 (specs/per-geolocation-ubigeo-postal-code.md).