works correctly and one hopes with enough performance now

the fly in the ointment was that authenication is a "transactional"
conversation between the client and the server that does not follow
the usual call/response pattern that everything else does

this is now resolved by determining when we are authentication, and
when we are then do a more expensive search through the server response
for when the cached command split state can be reset, otherwise
just reset as soon as the server starts talking back