Integrator is available remotely today. They say Old was a commissioning branch and the supplied folder is only the main routine export.

Then have them label the screenshots as historical and supply the complete current set, including the external inspection recipe references; a renamed main routine doesn't establish which other files it needs.

Include the ordinary PLC interface definitions and expected sequence states too, with the safety documentation referenced separately rather than reconstructed from screenshots.

They've sent a fuller export with both subroutines. Current main calls CheckHousing, which calls a shared measurement helper. That helper was missing from the original folder too.

That demonstrates why a dependency inventory matters, thanks for checking the actual calls; I'd still have them confirm the export corresponds to the running configuration rather than merely being their latest laptop copy.

A complete-looking directory is not yet a verified recovery package. Ask for a documented comparison with the installed versions and an appropriate restore verification plan. Do not use a production restore as a casual test of the folder.

Integrator has compared the file versions with the installed set during the session and attached the fixture and recipe references. Restore verification is being scheduled, not claimed complete.

Can I ask who will maintain that manifest after the next recipe change?

Controls lead owns it. I've added that name to the handover and kept the old screenshots out of the current recovery pack.

Give the shift team the location of the approved pack as well. A good manifest buried in the integrator's email is still a treasure hunt when the machine is down.