I am not sure if it’s easy to make existing suites, like, shard_merge_jscore_passthrough.yml, to run QE workloads (OR)
it would require us to introduce new suite “shard_merge_FLE2_jscore_passthrough.yml” (similar to shard_merge_multi_stmt_txn_jscore_passthrough.yml).

Option1, the workflow will be

1) This Ticket: Make changes to shardmergeFixture to support QE workload.
2) This Ticket: Locally test those js changes by disabling this class (which disables migration) in shard_merge_jscore_passthrough.yml
3) Wait for the c++ merge fix to go in.
4) This Ticket: Commit the js changes.

Option#2, the workflow will be

1) This Ticket:: Do changes to shardmergeFixture to support QE workload and test it via new suite - “shard_merge_FLE2_jscore_passthrough.yml (w/o ContinuousShardMerge hook). Finally commit this js changes.
2) C++ Ticket: c++ merge fix goes in which will enable ContinuousShardMerge hook in shard_merge_FLE2_jscore_passthrough.yml.