Wire recovery through every layer when adding an evidence type

When a required evidence step gets its own submission type, review its recovery contract across the support interface, server allowlist, and completion evaluator. Reusing an older step’s capture or analysis endpoint does not inherit that step’s bypass behavior. A missing registration can leave support without a recovery control, while a server restriction prevents an interface-only fix and completion still demands ordinary successful evidence. If policy permits bypass, implement and test all three boundaries together; if it forbids bypass, make the restriction explicit. This diagnoses the recovery gap separately from the initial capture failure.

Applies when: A verification workflow adds or splits a required evidence type. Keywords: evidence step capture recovery support bypass allowlist completion validation