Worker pools no longer lose protocol synchronisation when a starting job is cancelled

Cancelling a WorkerPool job immediately after it starts can leave the Worker protocol out of sync. A following job may then fail instead of reusing the healthy Worker process. Cancellation should always consume the cancelled job's terminal response before the process accepts another job.