There will inevitable be instances, hopefully just in dev environments, when the mite status is dirty, but you don't want to step down to the bottom and then back up for some reason.
mite resolve would "fix" any dirty migrations by updating the migration hash in the database to match what's on disk. This could get nasty if you abuse it, so there definitely needs to be a confirmation prompts/flags.
mite resolve should resolve any dirty migrations (and the prompt should list them)
mite resolve whatever.sql should only resolve the specified migration.
There will inevitable be instances, hopefully just in dev environments, when the mite status is dirty, but you don't want to step down to the bottom and then back up for some reason.
mite resolvewould "fix" any dirty migrations by updating the migration hash in the database to match what's on disk. This could get nasty if you abuse it, so there definitely needs to be a confirmation prompts/flags.mite resolveshould resolve any dirty migrations (and the prompt should list them)mite resolve whatever.sqlshould only resolve the specified migration.