why are scripts in afterMigration re-run even if unmodified?

[wizofaus]

My understanding was that grate would never re-run a script that had been run before and not modified since. Certainly that seems to be true of all the directories we had been using until recently when I put a script in afterMigration where I wanted to do a one-time execution of a new stored procedure (that was under sprocs in the same deployment). But the script has been re-executed on each deployment since, which caused an issue with one of our customers. Should I use runAfterOtherAnyTimeScripts instead? Or is there a flag I can pass to grate to stop it running unmodified scripts in afterMigration?
(this was literally a 1-time migration we needed to do, so for now we just removed the script, but for future reference we just wanted to know if "runAfterOtherAnyTimeScripts" script are never re-executed if unmodified in subsequent deployments?)

[wokket]

Per https://grate-devs.github.io/grate/getting-started/#directory-run-order afterMigration is an everytime folder (just like RH).

runAfterOtherAnyTime will work for you, or there's a way to override the run mode per folder at the commandline (Docced at https://grate-devs.github.io/grate/folder-configuration/ ).

EDIT: We have support for naming a file with *.everytime.* to force an everytime behaviour regardless of folder config, but we don't have equivalent support for *.anytime.*.... I wonder if that's a back-compt hole compared to Roundhouse?