I can easily split off some code developed during research into its own reusable app, library, or package

For example, if we develop a new turbulence model in the BL project, can I make it into an extension library and keep using it to generate the research artifacts, but allow others to use it?

```sh
calkit new python-package ...
```

Should a package always have a dev repo to prototype and store evidence for new features? Should the packages become Calkit projects to run those prototyping pipelines?

Start with the questions in this issue and inspect the `calkit new python-package ...` entry point and its documentation. Determine the supported workflow for extracting research code, prototyping in a development repository, and storing evidence; done means the package and project lifecycle is clearly decided and documented.

Written by the indexing model from the issue text.