test/csuite/schema_disagg_abort takes a -q option that gives every create a fresh table name, and Evergreen runs each of its shapes twice, once with name reuse and once with -q. The unique-name runs are a workaround: they exist so the rest of the schema behaviour can be exercised while create-drop-recreate of one table name still fails.

Once those failures are fixed, drop the workaround: remove the -q option and the generation counter behind it from the test, and remove the schema-disagg-abort-unique-* tasks from test/evergreen_disagg.yml. Name reuse is the stronger workload and should be the only one that runs.