Release v1.16.3

Changed

• The jobs documentation now explains what happens to a job step's state when the step succeeds, fails, is stopped or is removed, that PerformStep works on a snapshot of the state, and how to deliver outside input such as worker callbacks to a running job through the job's own grain. See https://github.com/Cratis/Orleans/blob/main/Documentation/concepts/jobs.md (#66)

Fixed

• A job step whose job is removed now has its stored state deleted. It used to be saved again and stay until the job's own state was cleared (#71)