Separate confirmed acceptance behavior from eligibility semantics

When translating a customer-requested verification step into implementation scope, separate confirmed acceptance behavior from unanswered eligibility semantics. Capture how mismatches and missing values should be handled, but do not infer which entity classes are eligible or whether an existing step is renamed or replaced when the source does not say.

Keep uncertain eligibility from blocking unrelated classes, and require product and repository confirmation before encoding those rules.