The client submits the same keys in mutations and write conflict ranges

It is going to be tricky to make an optimization based on this because of how read your writes handles write conflict ranges, but it might be worth the effort.

The issue names no files, tests, or entry points. Start by investigating how mutations, write conflict ranges, and read-your-writes interact in FoundationDB; completion would require a defined optimization, its correctness constraints, and evidence that the duplicate key submission is reduced without changing transaction behavior.

Written by the indexing model from the issue text.