[Randomname653]

What & why

The front end formatted numbers and dates with the browser's locale. On a German browser the Wrap-Up's graveyard read "1.055GB" (meaning 1,055 GB), right next to the curator's "3,152 GB". The owner asked for both to follow the language the user speaks to Curatarr in.

• services/user_language.py: the language the user writes to the curator in most.
  • It uses the detector the Wrap-Up writer already uses (wrapup_writer.main_language: stopwords over the last 300 messages, no model).
  • English when there are no messages. Read at most once an hour per user.
  • Mapped to an Intl locale (en-US, de-DE, fr-FR, …).
• The login (PIN poll) and /api/auth/status carry it as locale.
• ui.setLocale / ui.loc(): setUser sets it before anything renders. Every toLocaleString / toLocaleDateString / toLocaleTimeString call (81 in 14 files) now passes loc().
  • Before a session exists (setup, login), loc() is undefined, so the browser's own locale is used, as before.

Checks

• python tests/run_all.py is green (252/252)
• New tests/test_user_locale.py (8 checks):
  • English and mostly-German writers, and no messages;
  • the hourly re-read;
  • the auth payloads;
  • no toLocale* call left without loc();
  • setUser order;
  • de-DE 1.055 vs en-US 1,055.
• test_wrapup_story_mode's node harness stubs loc.

🤖 Generated with Claude Code