chore(autonomous-nodes): add examples to autonomous node docs

studio/concepts/nodes/autonomous-node.mdx

@@ -182,6 +182,31 @@ You can view a full list of tools your bot currently has access to in the [Inspe
     If you can't answer the user's question with `global.search`, use `browser.webSearch`.
     ```
   </Accordion>
+
+    <Accordion
+    title="Example: Keep knowledge and web search on-topic"
+    >
+
+    This prompt narrows when each search tool runs so the Node doesn't pull unrelated content:
+
+    ```markdown Instructions wrap
+    **Tool boundaries**
+    - Use `global.search` only for questions about [your scoped topic—for example course content or order support]. Do **not** use it for general pricing, marketing, or unrelated small talk unless the user explicitly needs a documented policy from the knowledge base.
+    - Use `browser.webSearch` only when `global.search` does not contain a sufficient answer **and** the question still falls within that same scope. Do not use web search for out-of-scope requests—politely decline instead.
+    ```
+  </Accordion>
+
+    <Accordion
+    title="Example: Video link with a timestamp"
+    >
+
+    When the base URL lives in a [Workflow variable](/studio/concepts/variables/scopes/workflow), this prompt tells the Autonomous Node how to add a start time (replace the variable name with one you have given the Node access to):
+
+    ```markdown Instructions wrap
+    **Video links**
+    If the user wants a link to the lesson video, the base URL is in `workflow.contentLinks`. To jump to a specific second, append a `t` query in seconds (e.g. 15 seconds → add `?t=15` or `&t=15` depending on whether the URL already has query parameters).
+    ```
+  </Accordion>
   </Tab>
   <Tab title="Transition tools">
     Here are the tools your bot uses to make transitions:
@@ -199,6 +224,30 @@ You can view a full list of tools your bot currently has access to in the [Inspe
       ```
     </Accordion>
 
+    <Accordion
+    title="Example: Transition and set a variable"
+    >
+
+    This pattern is for leaving the Autonomous Node for a structured sub-Workflow after saving a value from the conversation. The Autonomous Node needs [read and write access](#give-access-to-variables) to the variable you mention:
+
+    ```markdown Instructions wrap
+    When the user asks for deeper details about an email they mentioned, use `workflow.transition` to move to the **Enrich contact** Node. Before transitioning, set `workflow.requestedEmail` to that email address.
+    ```
+
+    Replace the Node name, variable name, and trigger phrase with whatever matches your bot.
+    </Accordion>
+
+    <Accordion
+    title="Example: Menu choice, then transition"
+    >
+
+    This prompt combines `global.Message` with `workflow.transition` when the user picks a numeric option. Connect each target with a **Transition** card on the canvas first so `workflow.transition` is valid:
+
+    ```markdown Instructions wrap
+    If the user sends **1**, thank them briefly with `global.Message`, then use `workflow.transition` to go to the **Self-serve** node. If they send **2**, use `workflow.transition` to go to the **Guided setup** node.
+    ```
+    </Accordion>
+
   </Tab>
   <Tab title="Integration tools">
     Any additional Cards you've added to the Autonomous Node also have their own tools that you can refer to directly. This includes Cards from external integrations.