Drush is a completely standard, virtually indispensable, tool for running Drupal sites. When getting or receiving support from other community members, I've never heard anybody ask "do you have Drush?" I feel like it's assumed. Even widely used development environments like DDEV have native support for it (ddev drush).
I'm sure we could look at the data if we wanted to, but pragmatically speaking, I don't think we really need to justify Drush's inclusion in Starshot. In fact, I think not including it would be an unpleasant surprise. To a completely new Drupal user, it might be invisible, but it wouldn't be long before they ran into a need for Drush, and it would be best if they didn't have to wrestle with the command line, and Composer, to get it.
The only question, I think, is whether it should be a runtime dependency, or a dev dependency.
Fixed
Code
I think this is crucial as it's also common practice to use drush during site deploy. Because of that I don't think it should be a dev dependency.
Automatically closed - issue fixed for 2 weeks with no activity.