History response checks are not always done

If a server on which session commands have been executed is slow enough that it hasn't executed a single command before history pruning takes place, it is possible that the response history is pruned too early. This means that the responses from the slow server for commands that were pruned are not verified. This can theoretically cause a inconsistency in session state on the slow server.

This is very unlikely to happen given the default value of 50 for max_sescmd_history.