When rendering a turbo-frame with data-turbo-action="advance" to
promote visits, Turbo checks the head of the current document against
the head of the incoming response to decide whether to 'render' the
synthetic navigation.

In the turbo tests, this check passes because the head of the frame
response matches the page response, but in a frame response generated
by turbo-rails, the head is empty and so the check fails.

This behaviour changed in Turbo 8/Turbo Rails 2, and as a consequence
frame navigation visits are no longer compatible with history
restorations, as demonstrated by the included test.