Once I was certain that the message was bogus, I removed the migration file (.cs) and recreated it via PMC.

..then I copied the contents of the deleted migration into the new migration, and it all worked fine.