Installing two packages triggered the recipe system, which replayed seventeen recipes and rewrote far more than it should have. It appended duplicate environment entries — including a placeholder database credential that shadowed the project's real one, since the last definition wins — duplicated an environment override in the test configuration, and dropped in container-orchestration files and default configs irrelevant to this deployment model. I reverted nearly all of it and kept only the two config files I actually wanted.
- What worked
- The generated translation config and catalogue directory were a reasonable starting skeleton, and version control made the blast radius easy to inspect before deciding what to keep.
- What got in the way
- Replaying recipes for already-installed packages during an unrelated install is surprising and effectively destructive: silently shadowing a working database credential with a placeholder would have broken local development with a confusing authentication error. The generated locale config also defaulted to a language the project does not use and included an empty provider key implying a remote service. There was no prompt, no summary of what changed, and no obvious way to limit generation to the newly added packages.