Pipeline: rename Location to City, wire postal code into breweries

docs/pipeline/ETHICS-AND-KNOWN-ISSUES.md

@@ -109,10 +109,10 @@ gender from the source data is preserved through to the sampled `Name`
 persona/bio generation later.
 
 The full multinational dataset is kept as-is (106 countries for forenames,
-75 for surnames) rather than trimmed to `locations.json`'s current country
+75 for surnames) rather than trimmed to `cities.json`'s current country
 list, so it doesn't need re-sourcing if more countries are added later.
 `SampleName()` (a free helper in `generate_users.cc`) returns no result for
-a country present in neither file; of the countries in `locations.json`,
+a country present in neither file; of the countries in `cities.json`,
 that's currently `KE`, `SE`, `SG`, `TH`, `VN`, and `ZA` — `GenerateUsers`
 skips cities in those countries the same way brewery generation skips
 cities whose enrichment lookup fails.
@@ -281,7 +281,7 @@ Output sample:
   a location's code is unlisted, skip `description_local` generation and fall
   back to English.
 - **Upstream sanitization:** strip known low-resource language codes from the
-  `locations.json` payload before generation.
+  `cities.json` payload before generation.
 - **Downstream flagging:** add a `description_local_confidence` column to the
   SQLite schema so downstream applications can filter or flag potentially
   hallucinated text by language tier.