Problem: When a parameter or header is identified through API Discovery and is not marked as mandatory, the system currently does not allow that field to accept an empty value by default. This forces users to manually edit the API definition just to enable an empty value, even though the field isn't required.

Expected behavior: If a discovered parameter/header is non-mandatory, the system should allow an empty value by default, with no need for manual changes to the definition.

Benefit: Less manual rework after each discovery run, fewer false-positive validation errors on optional fields, and more consistent, hands-off behavior overall.