Update docs upon changes to Bruno: v4.1.0 migration & mock URL notes

bru-lang/yaml-migration.mdx

@@ -71,7 +71,7 @@
 ## After migration
 
 - Your requests are now saved as `.yml` files with `opencollection.yml` at the collection root
-- If any scripts use `bru.runRequest()` with a `.bru` file extension in the path, update those to `.yml`
+- Any `bru.runRequest()` calls in your scripts that referenced a `.bru` path (for example, `bru.runRequest("folder/req.bru")`) are rewritten during migration to drop the `.bru` extension (`bru.runRequest("folder/req")`). Extensionless paths, comments, strings, and unrelated code are left unchanged.
 - The original `.bru` files are removed after migration, so keep your backup until you confirm everything works
 
 ## Related

mock-servers/run-mock-server.mdx

@@ -1,12 +1,12 @@
 ---
 title: "Run a Mock Server"
 sidebarTitle: "Run a Mock Server"
 description: "Run a mock server, interface walkthrough, server controls, request log, response examples, and more."
 ---
 
 Once you have created a mock server, you can run it by clicking the **Start Server** button in the mock server dashboard.
 
 ## Dashboard interface walkthrough 
 
 The mock opens as its own tab in the main pane (distinct from a request tab).
 
@@ -45,7 +45,7 @@
 
 #### Mock response editor
 Each mock response is presented as a first-class object with:
-  - **Method** and **Path** - path parameters use `:name` (for example, `/users/:id`)
+  - **Method** and **Path** - path parameters use `:name` (for example, `/users/:id`). Template variables such as `{{baseUrl}}` are preserved when you save the URL. Bruno strips only the base URL portion from the saved path, so route registration on the mock server still uses the resolved `:name` segments.
   - **Status** and **Headers**
   - **Expected** editor with syntax highlighting and expected response body
   - **Rules** - optional conditions that select one response over another for the same method + path
@@ -101,7 +101,7 @@
 <Tip>
 For nested body fields, you can use a dotted path with or without the `$` prefix. For example, both `user.type` and `$.user.type` are supported.
 
 Array indexing and advanced JSONPath filters are not currently supported.
 </Tip>
 
 #### Demo Request
@@ -151,7 +151,7 @@
 - Every mock response considered for the matched route
 - Each rule condition, with whether it passed or failed, and the actual value received (e.g., got `"guest"`)
 - Which response was selected and why - such as specific rules passing, or fallback/default logic
 - For unmatched requests, a list of available routes to help identify missing or misconfigured mocks
 
 The newest Request Log entry auto-expands the inspector, making it easy to debug exactly why a request matched (or didn’t). This is your primary resource for answering questions like, “Why didn’t my rule match?” or “Which conditions failed?”