Align cross-version reference details across repositories (2.13–2.17 and Preview)

- Show channel in the POST /tickets response example in 2.14 to 2.17,
  as the GET /tickets/{ticket_id} example already does.
- Write "Unix timestamp" in the six contacts_bulk_job timestamp
  descriptions in 2.17, matching the other repository.
- Say in Preview that the activity log previous_state and new_state
  fields carry enabled or disabled for IP allowlist changes, as 2.16
  and 2.17 already do.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: markdennis22

descriptions/0/api.intercom.io.yaml

@@ -29797,13 +29797,16 @@ components:
         previous_state:
           type: string
           nullable: true
-          description: The state before the change. `idle` or `occupied`, and null
-            when the Admin had not been classified yet.
+          description: The state before the change. `idle` or `occupied` for an
+            occupancy change, and null when the Admin had not been classified
+            yet; `enabled` or `disabled` for an IP allowlist change.
           example: idle
         new_state:
           type: string
           nullable: true
-          description: The state after the change. `idle` or `occupied`.
+          description: The state after the change. `idle` or `occupied` for an
+            occupancy change; `enabled` or `disabled` for an IP allowlist
+            change.
           example: occupied
         threshold_minutes:
           type: integer

descriptions/2.14/api.intercom.io.yaml

@@ -14070,6 +14070,7 @@ paths:
                       has_more: false
                     category: Back-office
                     is_shared: false
+                    channel: messenger
               schema:
                 "$ref": "#/components/schemas/ticket"
         '401':

descriptions/2.15/api.intercom.io.yaml

@@ -13361,6 +13361,7 @@ paths:
                       has_more: false
                     category: Back-office
                     is_shared: false
+                    channel: messenger
               schema:
                 "$ref": "#/components/schemas/ticket"
         '401':

descriptions/2.16/api.intercom.io.yaml

@@ -21040,6 +21040,7 @@ paths:
                       has_more: false
                     category: Back-office
                     is_shared: false
+                    channel: messenger
               schema:
                 "$ref": "#/components/schemas/ticket"
         '401':

descriptions/2.17/api.intercom.io.yaml

@@ -23608,6 +23608,7 @@ paths:
                       has_more: false
                     category: Back-office
                     is_shared: false
+                    channel: messenger
               schema:
                 "$ref": "#/components/schemas/ticket"
         '401':
@@ -29435,18 +29436,18 @@ components:
         created_at:
           type: integer
           format: date-time
-          description: The time the job was created as a UNIX timestamp.
+          description: The time the job was created as a Unix timestamp.
           example: 1713360000
         updated_at:
           type: integer
           format: date-time
-          description: The time the job was last updated as a UNIX timestamp.
+          description: The time the job was last updated as a Unix timestamp.
           example: 1713360060
         completed_at:
           type: integer
           format: date-time
           nullable: true
-          description: The time the job completed as a UNIX timestamp. Null if not
+          description: The time the job completed as a Unix timestamp. Null if not
             yet completed.
           example: 1713360120
         tasks:
@@ -29475,20 +29476,20 @@ components:
               created_at:
                 type: integer
                 format: date-time
-                description: The time the task was created as a UNIX timestamp.
+                description: The time the task was created as a Unix timestamp.
                 example: 1713360000
               started_at:
                 type: integer
                 format: date-time
                 nullable: true
-                description: The time the task started as a UNIX timestamp. Null if
+                description: The time the task started as a Unix timestamp. Null if
                   not yet started.
                 example: 1713360060
               completed_at:
                 type: integer
                 format: date-time
                 nullable: true
-                description: The time the task completed as a UNIX timestamp. Null
+                description: The time the task completed as a Unix timestamp. Null
                   if not yet completed.
                 example: 1713360120
         url: