Thanks for reporting this, can confirm that this is a bug on our end. We were incorrectly including the handshake bytes in the count.
We have a fix for this here that should be deployed shortly:
I’ll update this thread once the fix is out.
Once the fix is out, in the example you shared, for the first GETACK the expected response will be 31 (an ACK only includes bytes processed before the current GETACK).