Recover from target reset when doing remote execution
Recover from target reset when doing remote execution

Before I would try to copy a stack of -32 values... and go into the
weeds. Now I'm smarter about calculating how many values are on the
target's stack.

Twice, by forgetting to "pul" something I had "psh"ed into the S stack,
I caused a target reset and a weird "hang" in the interaction. This
fixes that.

nickhen/muforth,nickhen/muforth