In order to implement a mobile preview that displays the first suggested edit (as T258021: Variant C/D: mobile preview for suggested edits module with first suggested edit calls for) and have that first suggested edit actually match the the first edit in the queue that the user sees when navigating to the suggested edits module, we will need to somehow guarantee that the user sees the same suggested edits queue in these two situations.

One way to implement this could be to only request the queue from the server once, and reuse it on the client side. This would require client-side rendering of the mobile preview, and disallowing no-JS navigation to the suggested edits module (which makes some sense, since it's currently a JS-only module anyway).

If we render the mobile preview server-side, or allow no-JS browser navigation to the suggested edits module as a separate request, we'll need to implement some kind of queue consistency/freezing feature in the backend.