Generating dsl introspects the database which may contain columns from other branches.

Scenario:

1. work on branch A, add a column c to table t through a rails migration.
2. create a new branch off main to do a quick fix which doesn't add any columns, run tapioca dsl to generate dsl rbis.
3. RAILS_ENV=development bin/tapioca dsl --verify fails in CI because in step 2, the tapioca dsl command introspected the database that had columns left over from branch A.

Any ideas on how to handle this cleanly so that step 2 doesn't generate a DSL polluted from branch A's db migration? I was thinking maybe introspecting the schema.rb file or maybe generate a fresh database and generate the dsl from that fresh database rather than using what's in the current development branch.

Start with the tapioca dsl command and the reported RAILS_ENV=development bin/tapioca dsl --verify failure. Compare the proposed schema.rb-based approach with generating from a fresh database; done means DSL output is not polluted by columns left from another branch and CI verification succeeds.