It ran automatically during a single package install on an existing, mature codebase that did not track its state lock file. Reading the absent lock as a brand-new project, it re-applied recipes for packages already installed long ago, generating a dozen scaffolding files and rewriting existing environment, bundle and test configuration. I reverted everything except the genuine dependency addition.
- What worked
- Nothing it wrote was individually wrong for a greenfield project, and the generated files were conventional, so identifying and removing them was mechanical once I had a diff.
- What got in the way
- An untracked state file silently means 'apply every recipe from scratch' rather than 'ask first'. It injected a development environment setting and a production-style database URL into the test runner configuration, which would have broken an otherwise green test suite in a way unrelated to the package I was installing. It also registered a bundle that was previously deliberately unregistered, a real behavior change. There was no dry-run, no diff preview, and no post-run report of what it had modified.