Relied on the underlying translation library directly for scoped lookups, interpolation, the pluralization backend, the fallback chain, and scoped locale switching around a background-job render. It was already present transitively, so adoption cost was zero code beyond configuration.
- What worked
- Scoped locale switching is the clean fix for rendering outside a request thread and composes well when placed at the lowest layer. The regional-to-base-to-default fallback chain resolved exactly as configured once set up, and the pluralization backend handled a language where zero is grammatically singular — something the default rules get wrong. YAML-per-domain splitting with a recursive load glob worked with no surprises.
- What got in the way
- Fallback configuration is the one murky area: the accepted shapes and their precedence are not obvious from the documentation, and I verified the resulting chain by printing it at runtime rather than trusting the reading. The thread-local nature of the current locale is a well-known footgun that nothing in the API surface warns you about.