Resolve region codes to region names across all region facing surfaces

Repository: coach-pulse-admin-ui and coach-pulse-stores-ui
Severity: P1
Area: Platform, Enterprise Data, Location Data API

What we saw

Region is rendered from the regionCode field rather than the paired regionName field on the same record. The Location Data API supplies both: regionCode carries the internal key for a larger regional grouping of districts, for example RFNE, and regionName carries the human readable label for that same grouping, for example FS Northeast. Every surface that filters, groups, or labels by region is currently showing the key. RFNE is meaningful to Tapestry data engineering and to nobody on the sales floor or in the training organization.

Why it matters

Region is a scoping primitive in this platform, not a cosmetic label. Regional content buckets, regional admin workspaces, regional analytics cuts, and automatic regional assignment at sign in all resolve against the same grouping. When a Regional Training Admin selects a publishing scope from a list of four letter keys, the single control that decides which market receives a piece of content is being chosen from an unreadable menu.

There is a second and quieter cost. Europe currently carries uniformly mislabelled country coding that collapses European stores into the wrong geography in any regional cut. A code only label makes that class of defect invisible, because a wrong code looks exactly like a right one, while a wrong name is caught by the first person who reads it.

Recommended action

Treat regionCode as the join key and regionName as the display value throughout. Implement the resolution once, at a single point, rather than mapping at each call site, so a region added upstream renders correctly everywhere without a front end change.

Acceptance criteria

1. Every region facing label, filter, selector, axis, and export column renders regionName.
2. regionCode remains the join key. No join is switched to a name based match, consistent with the Employee ID rule that name based identifiers are a defect in integration design.
3. A record with a missing or empty regionName falls back to regionCode and raises a log entry rather than rendering blank or null.
4. Adding a region upstream requires no front end change to display correctly.
5. Region label behavior under localization is either confirmed to follow interface language or explicitly documented as English master data.

Test coverage

• The canonical pair RFNE / FS Northeast.
• A European store record, to confirm the country coding condition is now legible rather than hidden behind a key.
• A record with a null regionName.
• A district tier account and a regional tier account, to confirm the label is identical at both scopes.
• One export and one analytics cut, since those are the surfaces most likely to bypass a shared display component.

Dependencies and out of scope

Correcting the underlying European country coding sits with Tapestry data engineering and is tracked separately. This item is display resolution only and does not change any stored value.