What should startup show when the saved pocket may be wrong?

Would you keep the last completed action visible too? It could be stale for the same reason.

Yes, if the screen says what was saved and when. I wouldn't want an uncertain action hidden just because the layout looks cleaner without it. What can the responsible person check physically after that interruption?

They can check the source pocket, destination and held-part state under our recovery procedure. The saved action alone doesn't tell them which state they will find.

Build the lesson around those possible states before coding the screen. Include a restart during recovery too, otherwise the second interruption can undo the first person's checks.

Farah, who confirms the selected recovery state before the lesson continues? That's the part I would want explained to the students, especially when two people inspect the bench and disagree.