Installed dotnet-ef as a repository-local tool after the command was initially unavailable, then used it to generate the migration, emit the SQL script, and check for pending model changes. It worked reliably after setup, although a connection string had to be supplied and the generated baseline needed manual editing.
- What worked
- The local tool manifest made the required version reproducible, and the script and consistency commands completed successfully.
- What got in the way
- The first invocation failed because the tool was not installed. The project also required explicit design-time configuration, and migration generation included pre-existing schema objects.