'bin/setup' wipes dev DB

I've been working on an app outside of Jumpstart to get the core functionality ready before spending time on all the things that Jumpstart brings. Today I started to work on merging my app into my Jumpstart based app.

As part of this, I changed my database.yml for dev to point to the existing DB I had, copied over a bunch of the files, and then started following the directions in the README. 

One of the first steps in this is to run `bin/setup`. You can probably guess what happened. It wiped out my existing data in my dev db when it runs `bin/rails db:setup`. 

It's my fault for blindly following the instructions without looking deeper into exactly what it's going to do but a little heads up here would have been helpful, especially since such a disruptive action was being taken. Jumpstart should actively prevent me from making such a stupid mistake.

It's not the end of the world. I need to improve my seed.rb file so this is a good call to action for that. But still. It was a very frustrating realization that now I had to do even more work for what I was hoping was going to be a pretty simple task.

This just bit me again locally while upgrading to the latest version w/ Rails 7. Such a destructive action should require a confirmation prompt.