Requested the package and a cycle walkthrough. Current folder cannot identify which installed revision its pictures describe.

Keep that unknown visible in the request. A current export would give you a working reference without proving which older revision every picture came from.

Our laptop handover once omitted which configuration the normal shortcut loaded, so the right files still led people into the wrong setup. Ask how the ordinary user selects this plate job too, not only how the integrator opens it.

Export received and tied to installed revision. Walkthrough found an external recipe selection absent from the screenshots.

Who controls that recipe reference? It needs to remain connected to the program and fixture assumptions when one of them changes.

And show the normal maintainer where to find it. Naming a dependency in an index is not much use if only the integrator has access to the actual record.

Quality owns the recipe revision; maintenance can now reach the linked record from the handover. Interruption decisions still need review.

Use one existing interruption example for that review. Have the reader show where the documented decision ends, rather than ask them to invent the missing recovery step.