Drop email_verified value list from contact request descriptions

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: adisan19

descriptions/0/api.intercom.io.yaml

@@ -31024,10 +31024,6 @@ components:
                 description: |-
                   Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-                  - `true`: verified. Only send `true` when you have this proof.
-                  - `false`: not verified.
-                  - Omitted: new contacts are not verified; existing contacts keep their current value.
-
                   Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
                 example: true
               name:
@@ -31179,10 +31175,6 @@ components:
                 description: |-
                   Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-                  - `true`: verified. Only send `true` when you have this proof.
-                  - `false`: not verified.
-                  - Omitted: new contacts are not verified; existing contacts keep their current value.
-
                   Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
                 example: true
               name:
@@ -34974,10 +34966,6 @@ components:
           description: |-
             Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            - `true`: verified. Only send `true` when you have this proof.
-            - `false`: not verified.
-            - Omitted: new contacts are not verified; existing contacts keep their current value.
-
             Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         phone:
@@ -43375,10 +43363,6 @@ components:
           description: |-
             Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            - `true`: verified. Only send `true` when you have this proof.
-            - `false`: not verified.
-            - Omitted: new contacts are not verified; existing contacts keep their current value.
-
             Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         phone:

descriptions/2.16/api.intercom.io.yaml

@@ -28850,10 +28850,6 @@ components:
           description: |-
             Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            - `true`: verified. Only send `true` when you have this proof.
-            - `false`: not verified.
-            - Omitted: new contacts are not verified; existing contacts keep their current value.
-
             Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         email:
@@ -35669,10 +35665,6 @@ components:
           description: |-
             Whether the contact has proved they own this email address, for example through a confirmation link or one-time code you sent. Send it together with `email`. `email_verified` without `email` is rejected.
 
-            - `true`: verified. Only send `true` when you have this proof.
-            - `false`: not verified.
-            - Omitted: new contacts are not verified; existing contacts keep their current value.
-
             Changing a contact's email resets it to not verified. Intercom reuses leads with a verified email when an inbound email, conversation or ticket matches the address.
           example: true
         phone: