feat: Updated OpenAPI spec

src/libs/Speechify/Generated/Speechify.AgentClient.Delete.g.cs

@@ -45,8 +45,22 @@ partial void ProcessDeleteResponseContent(
 
         /// <summary>
         /// Delete Agent<br/>
-        /// Delete a voice agent. Conversations and attached tools remain. The<br/>
-        /// agent's tests are deleted with it; their run history is retained.<br/>
+        /// Delete an agent, and with it everything that belonged only to that<br/>
+        /// agent.<br/>
+        /// **Goes with the agent**, immediately unreadable through every<br/>
+        /// endpoint: its runs and their step journals and approvals, its<br/>
+        /// conversations and the transcripts, messages and recordings inside<br/>
+        /// them, what it learned about the people it spoke to, its triggers,<br/>
+        /// share links, channel bindings, team memberships and the batch<br/>
+        /// campaigns it dialled. A run that has not settled is asked to stop,<br/>
+        /// including one parked waiting on a person or on a delegated child. These are removed for good 30 days<br/>
+        /// later; until then the delete can still be walked back by support.<br/>
+        /// **Survives the agent**, because it belongs to the workspace rather<br/>
+        /// than to this agent: attached tools, knowledge bases, stores and<br/>
+        /// skills (only the attachment is dropped), the agent's tests, phone<br/>
+        /// numbers, and the teams it belonged to.<br/>
+        /// **Kept regardless**, because it is accounting rather than content:<br/>
+        /// the usage the workspace was billed for.<br/>
         /// Refused with `409 agent_in_use` while a live phone number still<br/>
         /// routes to the agent, including the agent a webhook binding<br/>
         /// provisioned for its number; `used_by` names the numbers. Unbind them<br/>
@@ -75,8 +89,22 @@ partial void ProcessDeleteResponseContent(
         }
         /// <summary>
         /// Delete Agent<br/>
-        /// Delete a voice agent. Conversations and attached tools remain. The<br/>
-        /// agent's tests are deleted with it; their run history is retained.<br/>
+        /// Delete an agent, and with it everything that belonged only to that<br/>
+        /// agent.<br/>
+        /// **Goes with the agent**, immediately unreadable through every<br/>
+        /// endpoint: its runs and their step journals and approvals, its<br/>
+        /// conversations and the transcripts, messages and recordings inside<br/>
+        /// them, what it learned about the people it spoke to, its triggers,<br/>
+        /// share links, channel bindings, team memberships and the batch<br/>
+        /// campaigns it dialled. A run that has not settled is asked to stop,<br/>
+        /// including one parked waiting on a person or on a delegated child. These are removed for good 30 days<br/>
+        /// later; until then the delete can still be walked back by support.<br/>
+        /// **Survives the agent**, because it belongs to the workspace rather<br/>
+        /// than to this agent: attached tools, knowledge bases, stores and<br/>
+        /// skills (only the attachment is dropped), the agent's tests, phone<br/>
+        /// numbers, and the teams it belonged to.<br/>
+        /// **Kept regardless**, because it is accounting rather than content:<br/>
+        /// the usage the workspace was billed for.<br/>
         /// Refused with `409 agent_in_use` while a live phone number still<br/>
         /// routes to the agent, including the agent a webhook binding<br/>
         /// provisioned for its number; `used_by` names the numbers. Unbind them<br/>

src/libs/Speechify/Generated/Speechify.ContactsClient.Delete.g.cs

@@ -53,9 +53,21 @@ partial void ProcessDeleteResponseContent(
         /// and has to be fired once per agent and once per channel; this reaches<br/>
         /// all of them, because "everything about this person" is a question the<br/>
         /// contact model can answer.<br/>
-        /// Conversations survive - they are the billing and forensic record - but<br/>
-        /// the facts extracted from them, and the copies of those facts frozen<br/>
-        /// into past prompts, do not.<br/>
+        /// Their calls, chats and durable runs are scrubbed rather than deleted,<br/>
+        /// the same way and for the same reason: the row keeps its id, status,<br/>
+        /// timings and usage - the accounting the workspace was billed on, which<br/>
+        /// is not the person's to erase - and loses everything that describes<br/>
+        /// them. For a call that means the transcript, the identity, the phone<br/>
+        /// numbers, the frozen prompt and variables; for a run, the instruction,<br/>
+        /// the variables, the output and every journalled step. The facts<br/>
+        /// extracted from either, and the copies frozen into past prompts, go<br/>
+        /// with them.<br/>
+        /// A recording stops being served from the moment of the request, and a<br/>
+        /// call still in progress can no longer append to its transcript, so a<br/>
+        /// turn that lands after the erasure cannot put the person back. The<br/>
+        /// audio itself is not yet collected from storage - that is tracked<br/>
+        /// separately - so treat the erasure as complete for every API surface<br/>
+        /// and pending for the stored bytes.<br/>
         /// The identifiers are tombstoned as part of the purge, which is what<br/>
         /// stops the person's phone number ever resolving again: a later merge<br/>
         /// naming the purged contact moves rows that are already dead rather than<br/>
@@ -98,9 +110,21 @@ partial void ProcessDeleteResponseContent(
         /// and has to be fired once per agent and once per channel; this reaches<br/>
         /// all of them, because "everything about this person" is a question the<br/>
         /// contact model can answer.<br/>
-        /// Conversations survive - they are the billing and forensic record - but<br/>
-        /// the facts extracted from them, and the copies of those facts frozen<br/>
-        /// into past prompts, do not.<br/>
+        /// Their calls, chats and durable runs are scrubbed rather than deleted,<br/>
+        /// the same way and for the same reason: the row keeps its id, status,<br/>
+        /// timings and usage - the accounting the workspace was billed on, which<br/>
+        /// is not the person's to erase - and loses everything that describes<br/>
+        /// them. For a call that means the transcript, the identity, the phone<br/>
+        /// numbers, the frozen prompt and variables; for a run, the instruction,<br/>
+        /// the variables, the output and every journalled step. The facts<br/>
+        /// extracted from either, and the copies frozen into past prompts, go<br/>
+        /// with them.<br/>
+        /// A recording stops being served from the moment of the request, and a<br/>
+        /// call still in progress can no longer append to its transcript, so a<br/>
+        /// turn that lands after the erasure cannot put the person back. The<br/>
+        /// audio itself is not yet collected from storage - that is tracked<br/>
+        /// separately - so treat the erasure as complete for every API surface<br/>
+        /// and pending for the stored bytes.<br/>
         /// The identifiers are tombstoned as part of the purge, which is what<br/>
         /// stops the person's phone number ever resolving again: a later merge<br/>
         /// naming the purged contact moves rows that are already dead rather than<br/>

src/libs/Speechify/Generated/Speechify.EndpointsClient.ListDeliveries.g.cs

@@ -56,7 +56,14 @@ partial void ProcessListDeliveriesResponseContent(
         /// (`last_status_code`, `last_response_body`, `last_response_headers`), so<br/>
         /// you can verify the signature and debug failures. Cursor-paginated: omit<br/>
         /// `cursor` for the first page; walk pages while `has_more` is true (default<br/>
-        /// page size 50, max 200).
+        /// page size 50, max 200).<br/>
+        /// An endpoint that was not a target of an event has no row for it: a<br/>
+        /// project-scoped endpoint records nothing for another project's events.<br/>
+        /// An empty list therefore means either nothing matched or nothing<br/>
+        /// happened. To tell them apart, list the project's own activity first<br/>
+        /// (`GET /v1/agents/runs?project_id=…`, the conversations list): activity<br/>
+        /// there with no delivery here is a defect to report; none there means<br/>
+        /// there was nothing to deliver.
         /// </summary>
         /// <param name="webhookEndpointId"></param>
         /// <param name="cursor"></param>
@@ -95,7 +102,14 @@ partial void ProcessListDeliveriesResponseContent(
         /// (`last_status_code`, `last_response_body`, `last_response_headers`), so<br/>
         /// you can verify the signature and debug failures. Cursor-paginated: omit<br/>
         /// `cursor` for the first page; walk pages while `has_more` is true (default<br/>
-        /// page size 50, max 200).
+        /// page size 50, max 200).<br/>
+        /// An endpoint that was not a target of an event has no row for it: a<br/>
+        /// project-scoped endpoint records nothing for another project's events.<br/>
+        /// An empty list therefore means either nothing matched or nothing<br/>
+        /// happened. To tell them apart, list the project's own activity first<br/>
+        /// (`GET /v1/agents/runs?project_id=…`, the conversations list): activity<br/>
+        /// there with no delivery here is a defect to report; none there means<br/>
+        /// there was nothing to deliver.
         /// </summary>
         /// <param name="webhookEndpointId"></param>
         /// <param name="cursor"></param>

src/libs/Speechify/Generated/Speechify.IAgentClient.Delete.g.cs

@@ -6,8 +6,22 @@ public partial interface IAgentClient
     {
         /// <summary>
         /// Delete Agent<br/>
-        /// Delete a voice agent. Conversations and attached tools remain. The<br/>
-        /// agent's tests are deleted with it; their run history is retained.<br/>
+        /// Delete an agent, and with it everything that belonged only to that<br/>
+        /// agent.<br/>
+        /// **Goes with the agent**, immediately unreadable through every<br/>
+        /// endpoint: its runs and their step journals and approvals, its<br/>
+        /// conversations and the transcripts, messages and recordings inside<br/>
+        /// them, what it learned about the people it spoke to, its triggers,<br/>
+        /// share links, channel bindings, team memberships and the batch<br/>
+        /// campaigns it dialled. A run that has not settled is asked to stop,<br/>
+        /// including one parked waiting on a person or on a delegated child. These are removed for good 30 days<br/>
+        /// later; until then the delete can still be walked back by support.<br/>
+        /// **Survives the agent**, because it belongs to the workspace rather<br/>
+        /// than to this agent: attached tools, knowledge bases, stores and<br/>
+        /// skills (only the attachment is dropped), the agent's tests, phone<br/>
+        /// numbers, and the teams it belonged to.<br/>
+        /// **Kept regardless**, because it is accounting rather than content:<br/>
+        /// the usage the workspace was billed for.<br/>
         /// Refused with `409 agent_in_use` while a live phone number still<br/>
         /// routes to the agent, including the agent a webhook binding<br/>
         /// provisioned for its number; `used_by` names the numbers. Unbind them<br/>
@@ -26,8 +40,22 @@ public partial interface IAgentClient
             global::System.Threading.CancellationToken cancellationToken = default);
         /// <summary>
         /// Delete Agent<br/>
-        /// Delete a voice agent. Conversations and attached tools remain. The<br/>
-        /// agent's tests are deleted with it; their run history is retained.<br/>
+        /// Delete an agent, and with it everything that belonged only to that<br/>
+        /// agent.<br/>
+        /// **Goes with the agent**, immediately unreadable through every<br/>
+        /// endpoint: its runs and their step journals and approvals, its<br/>
+        /// conversations and the transcripts, messages and recordings inside<br/>
+        /// them, what it learned about the people it spoke to, its triggers,<br/>
+        /// share links, channel bindings, team memberships and the batch<br/>
+        /// campaigns it dialled. A run that has not settled is asked to stop,<br/>
+        /// including one parked waiting on a person or on a delegated child. These are removed for good 30 days<br/>
+        /// later; until then the delete can still be walked back by support.<br/>
+        /// **Survives the agent**, because it belongs to the workspace rather<br/>
+        /// than to this agent: attached tools, knowledge bases, stores and<br/>
+        /// skills (only the attachment is dropped), the agent's tests, phone<br/>
+        /// numbers, and the teams it belonged to.<br/>
+        /// **Kept regardless**, because it is accounting rather than content:<br/>
+        /// the usage the workspace was billed for.<br/>
         /// Refused with `409 agent_in_use` while a live phone number still<br/>
         /// routes to the agent, including the agent a webhook binding<br/>
         /// provisioned for its number; `used_by` names the numbers. Unbind them<br/>

src/libs/Speechify/Generated/Speechify.IContactsClient.Delete.g.cs

@@ -14,9 +14,21 @@ public partial interface IContactsClient
         /// and has to be fired once per agent and once per channel; this reaches<br/>
         /// all of them, because "everything about this person" is a question the<br/>
         /// contact model can answer.<br/>
-        /// Conversations survive - they are the billing and forensic record - but<br/>
-        /// the facts extracted from them, and the copies of those facts frozen<br/>
-        /// into past prompts, do not.<br/>
+        /// Their calls, chats and durable runs are scrubbed rather than deleted,<br/>
+        /// the same way and for the same reason: the row keeps its id, status,<br/>
+        /// timings and usage - the accounting the workspace was billed on, which<br/>
+        /// is not the person's to erase - and loses everything that describes<br/>
+        /// them. For a call that means the transcript, the identity, the phone<br/>
+        /// numbers, the frozen prompt and variables; for a run, the instruction,<br/>
+        /// the variables, the output and every journalled step. The facts<br/>
+        /// extracted from either, and the copies frozen into past prompts, go<br/>
+        /// with them.<br/>
+        /// A recording stops being served from the moment of the request, and a<br/>
+        /// call still in progress can no longer append to its transcript, so a<br/>
+        /// turn that lands after the erasure cannot put the person back. The<br/>
+        /// audio itself is not yet collected from storage - that is tracked<br/>
+        /// separately - so treat the erasure as complete for every API surface<br/>
+        /// and pending for the stored bytes.<br/>
         /// The identifiers are tombstoned as part of the purge, which is what<br/>
         /// stops the person's phone number ever resolving again: a later merge<br/>
         /// naming the purged contact moves rows that are already dead rather than<br/>
@@ -49,9 +61,21 @@ public partial interface IContactsClient
         /// and has to be fired once per agent and once per channel; this reaches<br/>
         /// all of them, because "everything about this person" is a question the<br/>
         /// contact model can answer.<br/>
-        /// Conversations survive - they are the billing and forensic record - but<br/>
-        /// the facts extracted from them, and the copies of those facts frozen<br/>
-        /// into past prompts, do not.<br/>
+        /// Their calls, chats and durable runs are scrubbed rather than deleted,<br/>
+        /// the same way and for the same reason: the row keeps its id, status,<br/>
+        /// timings and usage - the accounting the workspace was billed on, which<br/>
+        /// is not the person's to erase - and loses everything that describes<br/>
+        /// them. For a call that means the transcript, the identity, the phone<br/>
+        /// numbers, the frozen prompt and variables; for a run, the instruction,<br/>
+        /// the variables, the output and every journalled step. The facts<br/>
+        /// extracted from either, and the copies frozen into past prompts, go<br/>
+        /// with them.<br/>
+        /// A recording stops being served from the moment of the request, and a<br/>
+        /// call still in progress can no longer append to its transcript, so a<br/>
+        /// turn that lands after the erasure cannot put the person back. The<br/>
+        /// audio itself is not yet collected from storage - that is tracked<br/>
+        /// separately - so treat the erasure as complete for every API surface<br/>
+        /// and pending for the stored bytes.<br/>
         /// The identifiers are tombstoned as part of the purge, which is what<br/>
         /// stops the person's phone number ever resolving again: a later merge<br/>
         /// naming the purged contact moves rows that are already dead rather than<br/>

src/libs/Speechify/Generated/Speechify.IEndpointsClient.ListDeliveries.g.cs

@@ -13,7 +13,14 @@ public partial interface IEndpointsClient
         /// (`last_status_code`, `last_response_body`, `last_response_headers`), so<br/>
         /// you can verify the signature and debug failures. Cursor-paginated: omit<br/>
         /// `cursor` for the first page; walk pages while `has_more` is true (default<br/>
-        /// page size 50, max 200).
+        /// page size 50, max 200).<br/>
+        /// An endpoint that was not a target of an event has no row for it: a<br/>
+        /// project-scoped endpoint records nothing for another project's events.<br/>
+        /// An empty list therefore means either nothing matched or nothing<br/>
+        /// happened. To tell them apart, list the project's own activity first<br/>
+        /// (`GET /v1/agents/runs?project_id=…`, the conversations list): activity<br/>
+        /// there with no delivery here is a defect to report; none there means<br/>
+        /// there was nothing to deliver.
         /// </summary>
         /// <param name="webhookEndpointId"></param>
         /// <param name="cursor"></param>
@@ -40,7 +47,14 @@ public partial interface IEndpointsClient
         /// (`last_status_code`, `last_response_body`, `last_response_headers`), so<br/>
         /// you can verify the signature and debug failures. Cursor-paginated: omit<br/>
         /// `cursor` for the first page; walk pages while `has_more` is true (default<br/>
-        /// page size 50, max 200).
+        /// page size 50, max 200).<br/>
+        /// An endpoint that was not a target of an event has no row for it: a<br/>
+        /// project-scoped endpoint records nothing for another project's events.<br/>
+        /// An empty list therefore means either nothing matched or nothing<br/>
+        /// happened. To tell them apart, list the project's own activity first<br/>
+        /// (`GET /v1/agents/runs?project_id=…`, the conversations list): activity<br/>
+        /// there with no delivery here is a defect to report; none there means<br/>
+        /// there was nothing to deliver.
         /// </summary>
         /// <param name="webhookEndpointId"></param>
         /// <param name="cursor"></param>