Better screenshot to point the values and the how the receiving window shrank with each recv
Notice the server has adjusted its receiving window to the exact received length after the client performed the full send, this is one perk of the Windows
TCP stack, dynamically resize, even it wasn't needed, but taking it as this socket had received this then it can
handle it again, on other side the window size sent by the client in the ACK, was shrinking until depletion, so server stopped sending and put the socket in not ready to send state, and it will wait until something from the client namely ACK ( being alone or combined with packet) to resume the socket state.
Also this behavior in the screenshot is on loopback, and it is different in few details when the NIC (Network Adapter and its driver) involved.