You may need to put that PRISMA_HIDE_UPDATE_MESSAGE=1 on the next command… do ENV vars stick around between commands when run with && between them?
Seeing that line says to me that Prisma thinks the migration hasn’t occurred yet and so is trying to run them from scratch again. But you said the tables are in the database at this point, correct? Is there anything in the _Migration table or is it empty? There should be a timestamp entry for every migration that has run against the database. It could be that the row isn’t being added to _Migration and so Prisma thinks no migrations have run yet and tries to run them again.
What would be hanging the process between creating the tables and inserting that row… no idea. 