confirmation-testing-workflow

The evidence procedure that justifies moving a defect out of Fixed: prove the build under test contains the fix, re-run the reproduction that failed before the fix, and classify the result.

What this owns, and what it does not

The axis is verification procedure vs lifecycle vocabulary: a lifecycle catalog owns the state names and legal transitions; this procedure owns the evidence that justifies picking one. It answers "may I claim Verified?", not "what states exist?". Out of scope: triage of the original defect (decided before a fix), severity and priority (separate axes, unchanged here), and the broader regression suite (a different activity - see below).

Confirmation testing is not regression testing

Both are change-related testing; conflating them is a common error.