docs(TSP-1348): add deletion audit events to streaming-events page

enterprise/streaming-events.mdx

@@ -18,7 +18,7 @@
 You don't need to run an OTEL collector to use this feature. Events are delivered directly to your S3 bucket where you can:
 
 - Query them directly using Athena, BigQuery, or similar tools
 - Ingest into your data lake (Snowflake, Databricks, etc.)
 - Forward to any OTEL-compatible backend for visualization and alerting
 
 <Note>Enterprise customers can enable PII redaction to automatically protect sensitive information in logs. Contact your Account Manager to learn more.</Note>
@@ -282,6 +282,16 @@
 | `relevance_ai.event.agent_id` | string | Yes | ID of the agent being published |
 | `relevance_ai.event.version_id` | string | Yes | ID of the version now live |
 
+### Conversation events
+
+**`conversation_deleted`** - Emitted when an agent conversation is deleted, covering both single deletions from the chat app and bulk deletions.
+
+| Attribute | Type | Required | Description |
+| --- | --- | --- | --- |
+| `relevance_ai.event.conversation_id` | string | Yes | ID of the deleted conversation |
+| `relevance_ai.event.agent_id` | string | Yes | ID of the agent the conversation belonged to |
+| `relevance_ai.event.workforce_task_id` | string | No | Workforce task ID, present when the conversation was part of a workforce execution. Use this to correlate with `workforce_task_deleted` events |
+
 ### Tool events
 
 **`tool_created`** - Emitted when a new tool is created (from scratch or cloned).
@@ -329,6 +339,7 @@
 | Attribute | Type | Required | Description |
 | --- | --- | --- | --- |
 | `relevance_ai.event.workforce_id` | string | Yes | ID of the deleted workforce |
+| `relevance_ai.event.workforce_type` | string | No | Whether the workforce was deleted directly (`"direct"`) or as a cascade side effect of deleting a chat task (`"cascade"`) |
 
 **`workforce_draft_saved`** - Emitted when work-in-progress changes are saved to a workforce.
 
@@ -344,6 +355,13 @@
 | `relevance_ai.event.workforce_id` | string | Yes | ID of the workforce being published |
 | `relevance_ai.event.version_id` | string | No | ID of the version now live |
 
+**`workforce_task_deleted`** - Emitted when a workforce task is deleted. This covers both single deletions from the chat app and bulk deletions via the Workforce UI.
+
+| Attribute | Type | Required | Description |
+| --- | --- | --- | --- |
+| `relevance_ai.event.workforce_id` | string | Yes | ID of the workforce the task belonged to |
+| `relevance_ai.event.workforce_task_id` | string | Yes | ID of the deleted workforce task |
+
 ### Permission events
 
 **`project_user_role_updated`** - Emitted when a user's role within a project is updated. This occurs when an admin changes another user's access level in the project settings.
@@ -503,7 +521,7 @@
 
 **Name**: `chat {model_name}`
 
 <Warning>This span was previously named `llm_completion`. If you have existing dashboards or queries filtering on `gen_ai.operation.name = "llm_completion"` or span names containing `llm_completion`, update them to use `"chat"`. The rename aligns with the [OpenTelemetry GenAI semantic conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/).</Warning>
 
 | Attribute | Type | Required | Description |
 | --- | --- | --- | --- |
@@ -523,7 +541,7 @@
 
 **Attribute**: `gen_ai.tool.definitions`
 
 <Warning>`gen_ai.tool.definitions` was previously an array type (`arrayValue`). It is now a JSON string (`stringValue`). If you consume this field in your pipeline or queries, you need to call `JSON.parse()` on the value to work with the tool definitions as structured data. The content is identical - the same tool definitions are present, just serialized as a string for better compatibility across OTEL exporters and backends.</Warning>
 
 ### `multi_agent_system_trigger`