Added a migration class in the project's existing migrations namespace for the queue table and related schema. A recipe-generated migrations config was unnecessary because the application already booted without it, so that file was removed. The new migration was not executed against the production database.
- What worked
- The existing migration class style was clear enough to add a versioned schema change without a new config file.
- What got in the way
- The migration was never applied, so up and down behavior on the production engine was not observed.