Transaction replay fails when session commands modify the server state inside it

The following SQL will fail to replay even though the results are similar:

BEGIN;

SET autocommit=0;

INSERT INTO test.t1 VALUES (1);

This is caused by the fact that the state of the session is changed by the set autocommit=0 statement which alters the status bytes the response to the BEGIN returns. The correct way to do this would be to execute any session commands inside the transaction in the same order the appeared in.