chore: Update API specifications with fern api update (2026-09-09T00-40-30-252Z)

fern/apis/api/openapi.json

@@ -6024,6 +6024,16 @@
                 }
               }
             }
+          },
+          "409": {
+            "description": "",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/PersonalityInUseConflictResponseDTO"
+                }
+              }
+            }
           }
         },
         "tags": [
@@ -6360,6 +6370,16 @@
                 }
               }
             }
+          },
+          "409": {
+            "description": "",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "$ref": "#/components/schemas/ScenarioInUseConflictResponseDTO"
+                }
+              }
+            }
           }
         },
         "tags": [
@@ -18145,7 +18165,7 @@
           },
           "callerId": {
             "type": "string",
-            "description": "This is the caller ID to use when transferring the call to the `number`.\n\nUsage:\n- If not provided, the caller ID will be the number the call is coming **from**.\n  Example: a customer with number +14151111111 calls in to and the assistant transfers out to +16470000000. +16470000000 will see +14151111111 as the caller.\n  For inbound calls, the caller ID is the customer's number. For outbound calls, the caller ID is the phone number of the assistant.\n- To change this behavior, provide a `callerId`.\n- Set to '{{customer.number}}' to always use the customer's number as the caller ID.\n- Set to '{{phoneNumber.number}}' to always use the phone number of the assistant as the caller ID.\n- Set to any E164 number to always use that number as the caller ID. This needs to be a number that is owned or verified by your Transport provider like Twilio.\n\nFor Twilio, you can read up more here: https://www.twilio.com/docs/voice/twiml/dial#callerid",
+            "description": "This is the caller ID to use when transferring the call to the `number`.\n\nUsage:\n- If not provided, the caller ID will be the number the call is coming **from**.\n  Example: a customer with number +14151111111 calls in to and the assistant transfers out to +16470000000. +16470000000 will see +14151111111 as the caller.\n  For inbound calls, the caller ID is the customer's number. For outbound calls, the caller ID is the phone number of the assistant.\n- To change this behavior, provide a `callerId`.\n- Set to '{{customer.number}}' to always use the customer's number as the caller ID.\n- Set to '{{phoneNumber.number}}' to always use the phone number of the assistant as the caller ID.\n- Set to any E164 number to always use that number as the caller ID. This needs to be a number that is owned or verified by your Transport provider like Twilio.\n\nNote: on Twilio, a caller who withheld their number has no caller ID the destination carrier will accept, so the assistant's phone number is presented instead and the transfer goes through. This applies when `callerId` is not provided and when it is set to '{{customer.number}}'.\n\nFor Twilio, you can read up more here: https://www.twilio.com/docs/voice/twiml/dial#callerid",
             "maxLength": 40
           },
           "transferPlan": {
@@ -59189,7 +59209,7 @@
             "maxLength": 80
           },
           "assistant": {
-            "description": "This is the full assistant configuration for this personality.",
+            "description": "Complete assistant replacement. Omitted credentials and redacted server secrets are preserved when their endpoint URL is unchanged. Send credentials: [] to clear credentials; omit a server container to remove it.",
             "allOf": [
               {
                 "$ref": "#/components/schemas/CreateAssistantDTO"
@@ -59205,6 +59225,25 @@
           }
         }
       },
+      "PersonalityInUseConflictResponseDTO": {
+        "type": "object",
+        "properties": {
+          "error": {
+            "type": "string",
+            "enum": [
+              "personality_in_use"
+            ]
+          },
+          "message": {
+            "type": "string",
+            "description": "Human-readable reason the personality cannot be deleted."
+          }
+        },
+        "required": [
+          "error",
+          "message"
+        ]
+      },
       "SimulationHookInclude": {
         "type": "object",
         "properties": {
@@ -59596,7 +59635,7 @@
             }
           },
           "targetOverrides": {
-            "description": "Overrides to inject into the simulated target assistant or squad",
+            "description": "Complete override replacement. Omitted credentials and redacted server secrets are preserved when their endpoint URL is unchanged. Send credentials: [] to clear credentials; omit a server container to remove it.",
             "example": {
               "variableValues": {
                 "customerName": "Alice",
@@ -59624,6 +59663,25 @@
           }
         }
       },
+      "ScenarioInUseConflictResponseDTO": {
+        "type": "object",
+        "properties": {
+          "error": {
+            "type": "string",
+            "enum": [
+              "scenario_in_use"
+            ]
+          },
+          "message": {
+            "type": "string",
+            "description": "Human-readable reason the scenario cannot be deleted."
+          }
+        },
+        "required": [
+          "error",
+          "message"
+        ]
+      },
       "SimulationRunSimulationEntry": {
         "type": "object",
         "properties": {