[maebeale]

🤖 suggested review level: 5 Inspect 🔬 rewrites existing address + form-answer data; changes two importers

Countries and states arrive as free text from FileMaker, the LMS registration sheet, and pre-dropdown portal forms ("USA", "California", "CA - California", a province with no country), so one place shows up as several and the new dropdowns can't preselect them — one shared translator now fixes that for every import and for the data already in the portal.

• AddressTranslation — country → a dropdown name; US state → USPS code; address type; locality.
  • A blank country is read from the state: a US state → United States, ON → Canada, England → United Kingdom.
  • Lookup tables only, never guessed (same rule as TagTranslation, ADR-0007).
  • A country it can't place is cleared and reported, so every stored country is a dropdown name or blank. The old value stays in the Ahoy log.
  • An unreadable state is kept and reported: state is required, and regions outside the US are legitimate.
• Imports — FmAddressAttributes (moved here from Import FileMaker organizations, programs, and affiliations #2788) builds every FileMaker address through it. Today that's the people import; after Import FileMaker organizations, programs, and affiliations #2788 rebases, the organizations and affiliations imports too. The LMS registration importer uses it as well. FileMaker's own fm_* tables stay raw.
  • The LMS import preview lists values the dropdowns don't offer (country left blank, state kept as typed), and the completion notice counts them.
• Existing data — data:translate_addresses (dry run by default) rewrites address countries/states and country/state form answers.
  • It fills a locality only where it's Unknown.
  • Every change is an autochange.* Ahoy event. Running it again changes nothing.
• No save hook — the dropdowns own new data.
• Form answers — country/state answers are now the one documented exception to "stored verbatim" (ADR-0009).

Prod runbook

1. Deploy, then bin/rails data:translate_addresses (dry run by default). Read the changes and the "nothing translates" list. Every run saves its report to storage and prints the read-back command.
2. Pick an import user in admin Settings (Imports) if none is set, then run DRY_RUN=false bin/rails data:translate_addresses. Every change is credited to that user.
3. Merge this PR, rebase Import FileMaker organizations, programs, and affiliations #2788, then run the FileMaker organizations import. It translates as it goes.
4. Run step 2 again to catch anything since.

🤖 Generated with Claude Code

[maebeale]

@jmilljr24 i'm merging now to check it out in staging