Document use draft chat tests and simulation suite duplication

fern/assistants/versioning/versioning-assistants.mdx

@@ -18,6 +18,19 @@ The assistant list and header show the selected version. A draft appears separat
   />
 </Frame>
 
+## Test draft changes in Chat
+
+In the assistant editor, select the down arrow next to **Talk**, then select **Chat**.
+
+<Frame caption="Open Chat from the menu next to Talk.">
+  <img
+    src="../../static/images/versioning/assistant-chat-menu.png"
+    alt="Assistant editor menu opened from the arrow next to Talk, with Chat as the first option"
+  />
+</Frame>
+
+Chat uses the unsaved configuration shown in the editor instead of the current published version, so you can test your changes before publishing.
+
 ## Publish a new version
 
 Publishing turns your current draft into a new version and makes it the **current** version.

fern/observability/simulations-manage.mdx

@@ -5,7 +5,7 @@ description: "Manage Vapi simulation suites and runs: edit configurations, revie
 slug: observability/simulations-manage
 ---
 
-Manage an existing simulation suite from the Dashboard or API. You can edit its configuration, review and rerun results, cancel an active run, maintain test coverage, or delete the suite. If you have not created a suite, complete the [**Simulations quickstart**](/observability/simulations-quickstart) first.
+Manage an existing simulation suite from the Dashboard or API. You can duplicate or edit its configuration, review and rerun results, cancel an active run, maintain test coverage, or delete the suite. If you have not created a suite, complete the [**Simulations quickstart**](/observability/simulations-quickstart) first.
 
 ## Edit a suite
 
@@ -31,6 +31,30 @@ To edit a scenario, personality, or simulation directly, use their own `PATCH` e
 </Tab>
 </Tabs>
 
+## Duplicate a suite
+
+Duplicating a suite creates an independent copy of its simulations, targets, and notification settings. The duplicate uses the original suite name with `(copy)` appended, and later changes do not affect the original suite.
+
+<Tabs>
+<Tab title="Dashboard">
+
+Open **Simulations**, select **Suites**, and open the suite. Open the suite actions menu, select **Duplicate**, then confirm. Vapi opens the duplicate after creating it.
+
+</Tab>
+<Tab title="cURL">
+
+Duplicate a suite with `POST`. The request does not require a body.
+
+```bash
+curl -X POST "https://api.vapi.ai/eval/simulation/suite/<suite-id>/duplicate" \
+  -H "Authorization: Bearer $VAPI_API_KEY"
+```
+
+The response contains the new simulation suite.
+
+</Tab>
+</Tabs>
+
 ## Rename an AI tester
 
 You cannot rename an AI tester from the Dashboard. An AI tester's name comes from its personality, so rename the tester with the API by updating the personality with `PATCH`. Send only the `name` field.