Having experimented a bit with UndoDB recordings, I've come to see they can be of great value in accelerating the debugging process, especially for non-deterministic behavior (e.g. concurrency bugs). That said, very few BFs right now have available recordings, and in many cases it's hard to reproduce a BF with non-deterministic behavior. I'm proposing that we add a new builder that captures recordings, and runs a small list of suites that exhibit non-deterministic behavior.

The hope would be that we can select a list of suites such that enabling the builder wouldn't significantly increase the latency of a patch build. If so, we can pilot the builder with a group of engineers and eventually roll it out as as a * or ! builder if it produces enough added value for us.

I have very little idea what sort of latency the different suites exhibit to know which ones are actually candidates for inclusion. But based solely on tested behavior, a suite list for initial evaluation might include some subset of:
aggregation_timeseries_fuzzer
concurrency_replication
concurrency_simultaneous
concurrency_simultaneous_replication_wiredtiger_cursor_sweeps
jstestfuzz_concurrent
jstestfuzz_concurrent_replication_write_conflicts
jstestfuzz_concurrent_sharded