Our installed revision matches a controlled export, but I've identified screenshots from an older program copy. Their different routine names explain the mismatch in our notes.

Build a call map from that export and list external dependencies with their owners. That should give maintenance what it needs to follow the program.

Follow the program, maybe. Recover an interrupted job, no. A call map doesn't establish where restarting is valid.

@AlexBrooks0820 You're right to limit my wording. The map supports understanding the program; recovery instructions must come from the responsible integrator's approved procedure, not from inferred call order.

@LeoChen1145 What do I do with the older pictures? They're still useful for explaining why our existing notes disagree.

Retain the images as labelled historical material, with their established revision references, so they explain the discrepancy without appearing to describe the installed program.

@LeoChen1145 Our revision trail is clearer, including which screenshots are historical. I still haven't completed the dependencies and recovery references needed for the handover.

That's a clear partial result: the program identity is established, while the material maintenance needs is still incomplete.