@jwilm Just running `script/cibuild` was actually the original behavior, and is still the default if you don't have a `dciy.toml`.

Breaking things out into "preparation" and "cibuild" opens up the possibility of providing different feedback if a preparation step fails as opposed to an actual test case failure, which might be useful. Having a build config file around will be handy if we want to support things like building across different environments and runtimes, say, and like you mentioned it does give us a place to stash build parameters when they come.

That being said, this is all fairly theoretical at the moment :wink: