Questionnaire Dropdown vs Global Metadata (KeyPointer) Value Mismatch

What This Skill Debugs

For dropdown (and multi-dropdown) questionnaire variables that map to global metadata (KeyPointer), the backend requires every stored choice value on the questionnaire side to exist as an option value on the global metadata KeyPointer — not merely the same label.

Product constraint (called out in incidents): In Metadata Manager, editing a dropdown option today can effectively change labels while leaving older values in place, reportedly for backward-compatibility reasons. Workflow Manager then validates the full questionnaire against global metadata and fails when QuestionVariable / FrozenQuestionVariable choices (values) are not a subset of KeyPointer.format_option.options[].value.

Confirmed backend error shape (API / validation):

The following choices are not present in the global metadata with name {label}: [...]

(Also: Global metadata with name {label} does not have any choices present if options are empty.)

Code (source of truth for the rule):