Resume-state predicates can turn expired evidence into a pre-submit client crash

General lesson: resume restoration and completion-currentness must use one coherent evidence-state contract. If a persisted artifact is accepted for display but considered non-current for completion, the client must explicitly route to recapture/review; it must not silently restore the artifact and then attempt a fallback resubmission without hydrating the analysis state that resubmission requires.

Applicability and limits: This applies to multi-step browser forms that persist OCR/photo evidence, resume from the server, and perform a final client-side reconciliation before a batch commit. It does not imply every generic submit error has this cause; corroborate with an immediate client exception and absence of the final API request.

Applies when: A resumed multi-step form has persisted evidence that is display-accepted but no longer valid for completion. Keywords: resume form expired evidence OCR fallback submit client crash