Both authors agree the request should remain until receipt; they disagree whether that receipt should also mean the coupon inspection is finished.

Give receipt and completion separate meanings, otherwise the sender cannot distinguish an accepted job still in progress from one whose result is available.

And show the trainee those separate states, not one 'ready' word doing three jobs.

Draft now names request received and result available separately, with an attempt identity; what should happen to an uncompleted attempt after the application restarts?

Reconcile that attempt with the other side before any retry; restart cannot establish that an accepted request did no work.

The offline test retains an accepted attempt across restart and asks for reconciliation instead of resending it, and the held request is received despite delayed polling.

Does the lesson explain who handles that reconciliation when you aren't there?

Sam, include Maya's handover question before station testing, along with repeated requests and delayed old results; the trainee needs an agreed contact and response, not permission to guess.