How do you check that saved API responses are complete before an offline replay?

A developer encountered an issue where an offline replay of saved API responses yielded an incorrect search-volume total of 65,240 instead of 67,140. This discrepancy was traced to a missing response file, as the replay path had only copied the first search-volume file. While adding the missing file corrected the total, the developer is seeking a more general completeness check to ensure all saved responses are present before starting a replay, rather than just validating the replay code.

This post moves beyond testing replay code to focus on validating the completeness of saved API responses, unlike typical discussions that only address replay logic.