Relaxed constrain on frequency for flusing report and added logging&report to client in case of mismatch between the report's type for the end of session and the presence of an error
Now we call reportEndOfSessionWithErrors if there is an actual error or a mismatch (that implies a bug in the code). Flushing is done as soon as the number of reports is >= frequency (instead of >)