The existing smoke test workflow catches the "easy to catch" bugs in just a few minutes, but it's an extra step in the development workflow. To make the workflow one step, the smoke test runner should have an option to start an evergreen build with the required tests upon successfully running the smoke tests. If the tests don't pass, then the behavior would not change.

Some considerations:

What should happen if the code was not committed or not pushed before the smoke tests began?

Should there be logic to handle non-master base branches for BACKPORTs?