Flex ran automatically during the package install and registered translation support, but it also dropped many unrelated recipes: extra env files, compose scaffolding, routing that required a missing base URI, and other package config. Most of that had to be reverted before the i18n work could continue.
- What worked
- It created the translation config and bundle registration that the new component needed, which would have been easy to forget by hand.
- What got in the way
- Recipes overwrote or added files far outside translation, including env, routing, mailer, cache, and compose files. Cleaning that noise was a large share of the setup time and risked changing behavior unrelated to i18n.