epic-stack: Deployment fails on 2nd deployment due to Prisma migration error

I just created a brand new Epic Stack to show someone how it worked. Ran through the setup following the docs and choosing the defaults. Deployed to Fly.io, which worked, and then setup a GitHub repo per the Deployment doc. Pushed the code and get a Prisma migration error.

Verified this by starting a new Epic Stack and doing it again, ensuring no code changes get made and following the instructions in the documentation. It also fails on the 1st push to GitHub (and the 2nd deployment to fly)

2024-01-17T03:50:11.294 app[***] den [info] level=INFO msg="executing command: npx [prisma migrate deploy]"

2024-01-17T03:50:13.191 app[***] den [info] Prisma schema loaded from prisma/schema.prisma

2024-01-17T03:50:13.209 app[***] den [info] Datasource "db": SQLite database "sqlite.db" at "file:/litefs/data/sqlite.db"

2024-01-17T03:50:13.358 app[***] den [info] 1 migration found in prisma/migrations

2024-01-17T03:50:13.376 app[***] den [info] Error: P3009

2024-01-17T03:50:13.376 app[***] den [info] migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve

2024-01-17T03:50:13.376 app[***] den [info] The `20230914194400_init` migration started at 2024-01-17 03:29:22.043 UTC failed

Is there potentially some secret that’s not getting set in Fly for the database location?