@testdriverai/mcp 7.11.135-test → 7.11.137-test

package/ai/skills/testdriver-assert/SKILL.md

@@ -6,7 +6,7 @@ description: Make AI-powered assertions about screen state
 
 ## Overview
 
-Make AI-powered assertions about the current screen state using natural language. The AI analyzes the screen and verifies that your assertion is true.
+Make assertions about the screen state with natural language and AI. The AI examines the screen. It makes sure that your assertion is true.
 
 ## Syntax
 
@@ -53,7 +53,7 @@ await testdriver.assert(assertion, options)
 
 ## Returns
 
-`Promise<boolean>` - `true` if assertion passes, throws error if assertion fails
+`Promise<boolean>` - `true` if the assertion passes. It throws an error if the assertion fails.
 
 ## Examples
 
@@ -100,7 +100,7 @@ await testdriver.assert('the modal dialog is open');
 <Check>
   **Assert state changes**
   
-  Verify state before and after actions:
+  Make sure of the state before and after actions:
   
   ```javascript
   // Before
@@ -310,5 +310,5 @@ describe('Assertions', () => {
 
 ## Related Methods
 
-- [`extract()`](/v7/extract) - Extract information for detailed assertions
-- [`find()`](/v7/find) - Locate elements to verify
+- [`extract()`](/extract) - Extract information for detailed assertions
+- [`find()`](/find) - Locate elements to verify

package/ai/skills/testdriver-caching/SKILL.md

@@ -4,7 +4,7 @@ description: How TestDriver learns your app and caches what it discovers for ins
 ---
 <!-- Generated from caching.mdx. DO NOT EDIT. -->
 
-Once the agent has [explored your app](/v7/generating-tests), TestDriver remembers what it found. Every element the AI vision agent discovers is cached with a vision fingerprint—a perceptual hash of the screen state where it was located. On the next run, TestDriver matches against that cache instead of calling the AI again. Passing tests replay instantly, deterministically, and cheaply.
+Once the agent has [explored your app](/generating-tests), TestDriver remembers what it found. Every element the AI vision agent discovers is cached with a vision fingerprint—a perceptual hash of the screen state where it was located. On the next run, TestDriver matches against that cache instead of calling the AI again. Passing tests replay instantly, deterministically, and cheaply.
 
 This learning is what makes TestDriver fast. Intelligent caching delivers up to **1.7x faster** test execution by skipping redundant AI vision analysis—the agent only thinks when it sees something new.
 
@@ -126,6 +126,6 @@ await testdriver.find(`order ${orderId} status`, {
 
 ## Next
 
-<Card href="/v7/copilot/running-tests" title="Run" icon="play">
+<Card href="/copilot/running-tests" title="Run" icon="play">
   Now that TestDriver has learned your app, run your tests in CI and locally—replaying the cache for fast, deterministic results.
 </Card>

package/ai/skills/testdriver-changelog/SKILL.md

@@ -0,0 +1,186 @@
+---
+name: testdriver:changelog
+description: Product updates and announcements
+---
+<!-- Generated from changelog.mdx. DO NOT EDIT. -->
+
+<Update label="v7.9.51-canary" description="April 2026" tags={["canary"]}>
+
+🚀 Canary release
+
+This release promotes changes from `v7.9.4-test` through `v7.9.51-test` to canary, rolling up all updates since `v7.9.3`.
+
+✨ New features
+
+- (Internal) **Autoscaling**
+- (Internal) **End-to-end distributed tracing**
+
+🔧 Improvements
+
+- **Faster image matching**
+- **Storage and infra hardening**
+- **Sentry environment consistency**
+- **Chrome extension interaction reliability**
+- **Docs and onboarding refresh** — Updated v7 docs, SDK examples, and VS Code onboarding/init flows.
+
+🐛 Bug fixes
+
+- **Windows AMI build stability** — Fixed `chrome.exe` startup/build failures.
+- **Realtime cleanup reliability** — Fixed connection cleanup leaks in session shutdown paths.
+- **Environment and deployment fixes** 
+
+</Update>
+
+<Update label="v7.8.0-test.22" description="March 2026" tags={["test"]}>
+
+Releases test.11 through test.22 include version bumps and internal CI improvements across all packages. No new user-facing changes — see [v7.8.0-test.10](#v780-test10) for the latest updates in this release stream.
+
+</Update>
+
+<Update label="v7.8.0-test.10" description="March 2026" tags={["test"]}>
+
+🔧 Improvements
+
+- **Parallel test concurrency** — Concurrency limits are now enforced with atomic slot tracking, eliminating a race condition where multiple tests launching at the same time could all bypass the limit. If you hit your concurrency cap, the SDK waits and retries automatically.
+- **Dashboard access for all plans** — Test recordings and metrics on the [dashboard](https://console.testdriver.ai) are now visible to all users, including those on the Free plan.
+- **Sandbox message throttling** — High-frequency interactions no longer risk hitting connection limits. The SDK automatically paces outgoing messages during fast command sequences.
+- **Windows Dashcam stability** — Web log tracking on Windows sandboxes now handles errors gracefully instead of failing the test.
+
+</Update>
+
+<Update label="v7.8.0-test.9" description="March 2026" tags={["test"]}>
+
+🔧 Improvements
+
+- **Stable release promotion** — Fixed an issue where promoting a test or canary release to stable could be incorrectly skipped. Stable releases now proceed reliably regardless of the prior pre-release channel.
+- **Example docs sync** — Example documentation now updates more reliably, continuing even when individual example tests fail so that passing examples still get refreshed.
+
+</Update>
+
+<Update label="v7.8.0-test.8" description="March 2026" tags={["test"]}>
+
+🔧 Improvements
+
+- **VS Code environment switching** — The TestDriver VS Code extension now includes a status bar indicator and a new **TestDriver: Switch Environment** command. You can switch between stable, canary, and test environments directly from VS Code, and your MCP server configuration updates automatically.
+- **Plan rename: Starter → Pro** — The "Starter" plan has been renamed to **Pro**. No changes to pricing or features — just a clearer name. The "Self-Hosted" tier is now labeled **Enterprise**.
+- **SDK network resilience** — API requests now automatically retry on transient server errors (500, 502, 503, 504) with exponential backoff, reducing flaky test failures caused by brief infrastructure hiccups.
+- **Pricing page refresh** — The [hosted plans page](/hosted) now shows plan cards with included minutes, concurrency limits, and pricing at a glance.
+
+📚 Docs updates
+
+- **Quickstart redesign** — The [quickstart](/quickstart) now has tabbed setup paths for CLI, GitHub Copilot, and manual installation.
+- **Deployment section** — "Cloud" is now [Hosted](/hosted) and the previous Enterprise page has been consolidated into [Self-Hosted](/self-hosted), which covers both standard and air-gapped deployments.
+
+</Update>
+
+<Update label="v7.8.0-test.7" description="March 2026" tags={["test"]}>
+This release includes all changes from v7.8.0-test.6 with version bumps across all packages. No additional user-facing changes.
+</Update>
+
+<Update label="v7.8.0-test.6" description="March 2026" tags={["test"]}>
+
+🔧 Improvements
+
+- **Sandbox spawning reliability** — Sandbox creation now uses a 3-minute timeout to handle slow infrastructure, then immediately switches to a 60-second orphan timeout for fast cleanup. This reduces sandbox creation failures during high-traffic periods.
+- **Command deadline timeouts** — Sandbox commands now enforce a hard deadline that terminates execution if the connection drops mid-command, preventing tests from hanging indefinitely.
+- **Real-time channel cleanup** — Fixed a compatibility issue with the real-time messaging layer that could cause channel cleanup to fail during shutdown.
+- **Dashboard timestamp tooltips** — Extended UTC date tooltips to the test history sidebar. Hovering over any relative timestamp (e.g., "5 minutes ago") across the [dashboard](https://console.testdriver.ai) now shows the full UTC date and time.
+
+</Update>
+
+<Update label="v7.8.0-test.4" description="March 2026" tags={["test"]}>
+
+✨ New features
+
+- **[GitHub Copilot integration](/copilot/running-tests)** — Use TestDriver directly from GitHub Copilot in VS Code. The new MCP server lets Copilot launch sandboxes, interact with elements, and run assertions through natural language. Includes guides for [creating tests](/generating-tests), [running tests](/copilot/running-tests), [GitHub Actions integration](/copilot/auto-healing#use-testdriver-in-github), and [auto-healing](/copilot/auto-healing).
+
+🔧 Improvements
+
+- **Sandbox reliability** — Linux sandboxes now use a longer creation timeout to handle slow infrastructure, then immediately switch to a short orphan timeout for fast cleanup of disconnected sessions.
+- **Command execution timeouts** — Sandbox commands now have deadline timeouts that prevent hangs if the connection drops mid-execution.
+- **Real-time connection stability** — Updated the real-time messaging layer for better compatibility and more reliable channel cleanup during shutdown.
+- **Dashboard date display** — Hovering over relative timestamps (e.g., "5 minutes ago") now shows the full UTC date and time.
+
+</Update>
+
+<Update label="v7.8.0-canary.5" description="March 2026" tags={["canary"]}>
+This release includes all changes from v7.8.0-canary.4 with version bumps.
+
+✨ New features
+
+- **[Cache API](/cache)** — Speed up repeated test runs with screenshot-based caching. The system compares screenshots to cached results and reuses element positions when the screen hasn't changed, reducing AI calls.
+- **[Custom error classes](/errors)** — New `ElementNotFoundError` class with rich debugging info including screenshot paths, pixel diffs, and detailed messages.
+- **[Events system](/events)** — Listen to SDK lifecycle events with wildcard support via `testdriver.emitter`. Uses colon-delimited namespaces (e.g., `command:start`, `log:*`).
+- **[Provision API](/provision)** — Launch browsers, desktop apps, VS Code, and Chrome extensions in your sandbox before tests run. Access via `testdriver.provision.*`.
+- **[Redraw detection](/redraw)** — Wait for screens to stabilize after interactions using two-phase detection with pixel comparison and z-score analysis.
+- **[Screenshots API](/screenshots)** — Capture screenshots manually with `testdriver.screenshot()` or automatically before/after every command.
+
+📚 New examples
+
+- [Exec output](/examples/exec-output) — Capture and use output from PowerShell commands
+- [Exec PowerShell](/examples/exec-pwsh) — Generate dynamic data with PowerShell
+- [Focus window](/examples/focus-window) — Switch focus between application windows
+
+🔧 Improvements
+
+- Improved console URL mapping for canary and test environments
+- Enhanced Ably channel cleanup for better resource management
+- Updated release workflow with improved changelog generation
+</Update>
+
+<Update label="v7.5.26" description="March 2026" tags={["stable"]}>
+🚀 Stable release
+
+This release promotes v7.5.25 to stable with deployment channel improvements.
+
+✨ Features
+
+- **Deployment channels** — SDK now supports stable and canary release channels. Stable releases use the `latest` npm tag, while canary releases use the `canary` tag. Install canary with `npm install testdriverai@canary`.
+
+🔧 Improvements
+
+- Improved cache hit debugging and logging
+- Enhanced element location reliability
+- Better error handling during test execution
+
+🐛 Bug fixes
+
+- Fixed restart behavior during auto-updates
+- Fixed console URL routing for various environments
+
+<Note>
+This release includes changes from v7.5.17 through v7.5.25.
+</Note>
+</Update>
+
+<Update label="v7.5.25" description="March 2026" tags={["stable"]}>
+🐛 Bug fixes
+
+- Fixed restart update behavior
+</Update>
+
+<Update label="v7.5.24" description="March 2026" tags={["stable"]}>
+🔧 Improvements
+
+- Disabled auto-update restart to improve CI stability
+</Update>
+
+<Update label="v7.5.22" description="March 2026" tags={["stable"]}>
+🔧 Improvements
+
+- Added markdown-to-HTML rendering for marketing content
+</Update>
+
+<Update label="v7.5.19" description="March 2026" tags={["stable"]}>
+🔧 Improvements
+
+- Enhanced debugging output for cache hits
+- Improved element location reliability
+</Update>
+
+<Update label="v7.5.17" description="March 2026" tags={["stable"]}>
+🔧 Improvements
+
+- Improved codespace scaling and development environment setup
+- Updated VS Code extension version
+</Update>

package/ai/skills/testdriver-claude-mcp-plugin/SKILL.md

@@ -0,0 +1,208 @@
+---
+name: testdriver:claude-mcp-plugin
+description: claude-mcp-plugin
+---
+<!-- Generated from claude-mcp-plugin.mdx. DO NOT EDIT. -->
+
+TestDriver ships as a native [Claude Code plugin](https://docs.claude.com/en/docs/claude-code/plugins) that bundles the **TestDriver MCP server**, the **`testdriver` expert sub-agent**, and all **TestDriver skills**. You get everything you need to drive TestDriver from Claude Code with a single install.
+
+> The plugin lives inside the `testdriverai` npm package at `ai/.claude-plugin/plugin.json`, and the marketplace entry lives at `.claude-plugin/marketplace.json` in this repo.
+
+## 1. Get a TestDriver API key
+
+- Visit your team page (e.g. `https://console.testdriver.ai/settings`)
+- Create or copy a **Team API Key** (or User API Key)
+- Export it in your shell so Claude Code can pass it to the MCP server:
+
+  ```bash
+  export TD_API_KEY="your_api_key_here"
+  ```
+
+## 2. Install the plugin in Claude Code
+
+From inside Claude Code, add this repo as a plugin marketplace and install the `testdriver` plugin:
+
+```text
+/plugin marketplace add testdriverai/testdriverai
+/plugin install testdriver@testdriver
+```
+
+That registers three things:
+
+- **`testdriver` MCP server** — spawned via `npx -p testdriverai testdriverai-mcp`, with `TD_API_KEY` forwarded from your environment.
+- **`testdriver` sub-agent** — the TestDriver expert agent from `ai/agents/testdriver.md`. Invoke it with `@testdriver ...`.
+- **TestDriver skills** — every `ai/skills/testdriver-*` skill, auto-loaded by Claude Code.
+
+## 3. Write tests with the agent
+
+In a Claude Code session, delegate to the agent:
+
+```text
+@testdriver Write a test that signs into https://example.com and adds an item to the cart.
+```
+
+The agent will use the TestDriver MCP tools (`session_start`, `find`, `click`, `type`, `assert`, …) to interactively build a Vitest test, append generated code to your test file after every action, and run it with `vitest run` until it passes.
+
+For the full agent guide, see the [`testdriver` agent definition](https://github.com/testdriverai/testdriverai/blob/main/ai/agents/testdriver.md) and the [MCP workflow skill](https://github.com/testdriverai/testdriverai/blob/main/ai/skills/testdriver-mcp-workflow/SKILL.md).
+
+## Manual MCP configuration (no plugin)
+
+If you prefer not to use the plugin, you can register the MCP server manually in any MCP-compatible client (Claude Desktop, Cursor, VS Code, …):
+
+```json
+{
+  "mcpServers": {
+    "testdriver": {
+      "command": "npx",
+      "args": ["-p", "testdriverai", "testdriverai-mcp"],
+      "env": {
+        "TD_API_KEY": "${TD_API_KEY}"
+      }
+    }
+  }
+}
+```
+
+This is the same config the plugin wires up for you — the plugin just bundles it alongside the agent and skills.
+
+---
+
+## Observing test runs via HTTP MCP
+
+TestDriver also exposes **test results and analytics** over an HTTP MCP endpoint, so Claude Code (or any MCP-compatible client) can inspect your test runs, failures, and filters without provisioning a sandbox.
+
+### HTTP MCP endpoint contract
+
+The HTTP endpoint lives at:
+
+```text
+POST /api/v1/mcp
+```
+
+It expects the TestDriver API key in the `X-Api-Key` header (or `Authorization: Bearer <key>`).
+
+Common request shapes:
+
+- **List tools**
+
+```json
+{
+  "kind": "list_tools"
+}
+```
+
+- **Call a tool**
+
+```json
+{
+  "kind": "call_tool",
+  "tool": "list_test_runs",
+  "arguments": {
+    "status": "failed",
+    "page": 1,
+    "limit": 20
+  }
+}
+```
+
+Responses from tool calls follow the MCP content convention:
+
+```json
+{
+  "content": [
+    {
+      "type": "json",
+      "json": {
+        "testRuns": [],
+        "totalCount": 0,
+        "hasMore": false
+      }
+    }
+  ]
+}
+```
+
+### Available tools
+
+The MCP server advertises at least these tools in `list_tools`:
+
+- `list_test_runs`  
+  List recent TestDriver test runs for the current team, with filters and pagination.
+
+- `get_test_run_detail`  
+  Get a single test run and its test cases (including replay IDs / share keys when available).
+
+- `list_test_cases`  
+  List individual test cases for the team with status, duration, error messages, and replay info.
+
+- `get_filter_options`  
+  Get branch, suite, repo, filename, commit, status, platform, and test name options for building queries.
+
+### Pointing Claude Code at the HTTP MCP endpoint
+
+You can point Claude Code at the HTTP MCP endpoint using a JSON configuration similar to:
+
+```json
+{
+  "$schema": "https://schema.anthropic.com/mcp/servers.json",
+  "mcpServers": {
+    "testdriver-cloud": {
+      "type": "sse",
+      "url": "https://your-api-host.example.com/api/v1/mcp",
+      "requestHeaders": {
+        "X-Api-Key": "${TD_API_KEY}"
+      },
+      "description": "Query TestDriver test runs, test cases, and filters for your team using an API key."
+    }
+  }
+}
+```
+
+You can find this exact snippet in the repo at:
+
+- `claude-mcp-config.example.json`
+
+Replace `https://your-api-host.example.com` with your actual API origin (e.g. `https://api.testdriver.ai` or `http://localhost:1337` in development).
+
+### Local development
+
+For local development:
+
+- Run your API server on `http://localhost:1337`
+- Point `baseUrl` at `http://localhost:1337/api/v1/mcp`
+- Use a local team or user API key in `TD_API_KEY`
+
+```json
+{
+  "mcpServers": {
+    "testdriver-cloud-local": {
+      "type": "sse",
+      "url": "http://localhost:1337/api/v1/mcp",
+      "requestHeaders": {
+        "X-Api-Key": "${TD_API_KEY}"
+      }
+    }
+  }
+}
+```
+
+### Skills documentation for Claude
+
+Claude Code loads the agent and skills automatically when you install the plugin (see step 2). The underlying sources are:
+
+- `ai/agents/testdriver.md` contains the **full TestDriver Agent Guide**
+- `ai/skills/testdriver-*/SKILL.md` provide task-specific skills (MCP workflow, assertions, provisioning, etc.)
+
+Use these as the primary reference for:
+
+- How to initialize the `TestDriver` SDK in Vitest
+- The MCP workflow for building tests interactively with visual feedback
+- How to find elements, click, type, scroll, assert, and capture screenshots
+
+The MCP tools described above are **read-only** helpers for:
+
+- Inspecting recent test runs and failures
+- Discovering branches, files, and suites to focus on
+- Pulling detailed test case and replay information into Claude for analysis
+
+Use the SDK (`testdriverai`) for **driving tests**, and the HTTP MCP server (`/api/v1/mcp`) for **observing and debugging** them from Claude Code.

package/ai/skills/testdriver-click/SKILL.md

@@ -6,7 +6,7 @@ description: Click at specific coordinates or on elements
 
 ## Element Click
 
-When called on an Element object, clicks on the located element.
+When you call this on an Element object, it clicks on the found element.
 
 ### Syntax
 
@@ -89,7 +89,7 @@ await testdriver.click(500, 300, 'right-click');
 
 ### Regular Click
 
-Single left-click action.
+One left-click action.
 
 ```javascript
 const button = await testdriver.find('Login button');
@@ -98,7 +98,7 @@ await button.click();
 
 ### Double Click
 
-Double-click action, commonly used to open files or select text.
+A double-click action. It usually opens files or selects text.
 
 ```javascript
 const file = await testdriver.find('document.pdf');
@@ -122,7 +122,7 @@ await folder.rightClick();
 
 ### Mouse Down / Mouse Up
 
-For drag operations or custom click behavior.
+Use these for drag operations or custom click behavior.
 
 ```javascript
 const draggable = await testdriver.find('draggable item');
@@ -141,9 +141,9 @@ await dropZone.mouseUp();
 ## Best Practices
 
 <Check>
-  **Prefer element clicks over coordinate clicks**
+  **Prefer element clicks to coordinate clicks**
   
-  Element-based clicking is more reliable and resolution-independent:
+  A click on an element is more reliable. It does not depend on the resolution:
   
   ```javascript
   // ✅ Preferred
@@ -156,7 +156,7 @@ await dropZone.mouseUp();
 </Check>
 
 <Check>
-  **Verify element was found**
+  **Make sure that TestDriver found the element**
   
   ```javascript
   const element = await testdriver.find('button');
@@ -168,9 +168,9 @@ await dropZone.mouseUp();
 </Check>
 
 <Warning>
-  **Element must be found before clicking**
+  **TestDriver must find the element before you click it**
   
-  The `find()` method automatically locates elements, but clicking an element that wasn't found will throw an error:
+  The `find()` method finds elements automatically. But a click on an element that TestDriver did not find throws an error:
   
   ```javascript
   const element = await testdriver.find('button');
@@ -280,7 +280,7 @@ describe('Click Interactions', () => {
 
 ## Related Methods
 
-- [`find()`](/v7/find) - Locate elements to click
-- [`hover()`](/v7/hover) - Hover without clicking
-- [`doubleClick()`](/v7/double-click) - Dedicated double-click method
-- [`rightClick()`](/v7/right-click) - Dedicated right-click method
+- [`find()`](/find) - Find elements to click
+- [`hover()`](/hover) - Put the cursor on the element without a click
+- [`doubleClick()`](/double-click) - The double-click method
+- [`rightClick()`](/right-click) - The right-click method

package/ai/skills/testdriver-client/SKILL.md

@@ -53,7 +53,7 @@ const testdriver = new TestDriver(apiKey, options)
     </ParamField>
     
     <ParamField path="reconnect" type="boolean" default="false">
-      Reattach to the last used sandbox instead of creating a new one. When `true`, the SDK reads the sandbox id from `.testdriver/last-sandbox` (written automatically on every successful connect) and rejoins that VM. Provision methods (`chrome`, `vscode`, `installer`, etc.) are skipped because the application is already running. The previous sandbox must still be alive — see [`keepAlive`](#keepalive) and the [Run guide](/v7/copilot/running-tests#keeping-machines-alive-between-runs).
+      Reattach to the last used sandbox instead of creating a new one. When `true`, the SDK reads the sandbox id from `.testdriver/last-sandbox` (written automatically on every successful connect) and rejoins that VM. Provision methods (`chrome`, `vscode`, `installer`, etc.) are skipped because the application is already running. The previous sandbox must still be alive — see [`keepAlive`](#keepalive) and the [Run guide](/copilot/running-tests#keeping-machines-alive-between-runs).
     </ParamField>
 
     <ParamField path="sandboxId" type="string">

package/ai/skills/testdriver-debugging-with-screenshots/SKILL.md

@@ -410,16 +410,16 @@ When tests fail or behave unexpectedly, replay what happened step by step:
 
 ## Where this fits in the Guide
 
-Debugging is what you reach for when a [Run](/v7/copilot/running-tests) goes sideways or a [Validate](/v7/making-assertions) assertion fails — the screenshots show you precisely what the AI saw before it acted. Once you've diagnosed the failure, the next step is to stop it from recurring.
+Debugging is what you reach for when a [Run](/copilot/running-tests) goes sideways or a [Validate](/making-assertions) assertion fails — the screenshots show you precisely what the AI saw before it acted. Once you've diagnosed the failure, the next step is to stop it from recurring.
 
 ## Related
 
-- [screenshot()](/v7/screenshot) - Capture screenshots during test execution
-- [Dashcam](/v7/dashcam) - Record full test sessions with video and logs
-- [assert()](/v7/assert) - Make AI-powered assertions that benefit from screenshot context
+- [screenshot()](/screenshot) - Capture screenshots during test execution
+- [Dashcam](/dashcam) - Record full test sessions with video and logs
+- [assert()](/assert) - Make AI-powered assertions that benefit from screenshot context
 
 ## Next
 
-<Card title="Prevent" icon="shield-check" href="/v7/copilot/auto-healing">
+<Card title="Prevent" icon="shield-check" href="/copilot/auto-healing">
   You've seen what went wrong — now keep it from happening again. Let auto-healing repair flaky tests automatically before they fail your suite.
 </Card>

package/ai/skills/testdriver-double-click/SKILL.md

@@ -6,7 +6,7 @@ description: Perform a double-click action on an element or at specific coordina
 
 ## Overview
 
-The `doubleClick()` method performs a double-click action on an element. You can either call it on an [`Element`](/v7/core-concepts/elements) instance or use it directly with a selector.
+The `doubleClick()` method does a double-click action on an element. You can call it on an [`Element`](/core-concepts/elements) instance. Or you can use it with a selector.
 
 ## Syntax
 
@@ -30,7 +30,7 @@ When called directly on the AI client:
 
 ## Returns
 
-Returns a `Promise<void>` that resolves when the double-click action completes.
+It returns a `Promise<void>`. The promise resolves when the double-click action completes.
 
 ## Examples
 
@@ -95,8 +95,8 @@ expect(selectedText).toBe('TestDriver');
 
 ## Related Methods
 
-- [`click()`](/v7/click) - Single click on an element
-- [`rightClick()`](/v7/right-click) - Right-click to open context menu
-- [`mouseDown()`](/v7/mouse-down) - Press mouse button without releasing
-- [`mouseUp()`](/v7/mouse-up) - Release mouse button
-- [`hover()`](/v7/hover) - Move mouse over element without clicking
+- [`click()`](/click) - Single click on an element
+- [`rightClick()`](/right-click) - Right-click to open context menu
+- [`mouseDown()`](/mouse-down) - Press mouse button without releasing
+- [`mouseUp()`](/mouse-up) - Release mouse button
+- [`hover()`](/hover) - Move mouse over element without clicking

package/ai/skills/testdriver-enterprise/SKILL.md

@@ -4,4 +4,4 @@ description: Self-hosted enterprise deployments with assisted setup and dedicate
 ---
 <!-- Generated from enterprise.mdx. DO NOT EDIT. -->
 
-This page has moved to [Self-Hosted](/v7/self-hosted).
+This page has moved to [Self-Hosted](/self-hosted).

package/ai/skills/testdriver-events/SKILL.md

@@ -155,7 +155,7 @@ testdriver.emitter.on('sandbox:progress', ({ step, message }) => {
 
 ### Redraw Events
 
-Emitted during screen stability detection. See [Redraw](/v7/redraw) for more details.
+Emitted during screen stability detection. See [Redraw](/redraw) for more details.
 
 | Event | Payload |
 |---|---|

package/ai/skills/testdriver-exec/SKILL.md

@@ -6,7 +6,7 @@ description: Execute shell or PowerShell commands in the sandbox
 
 ## Overview
 
-Execute shell commands (Linux) or PowerShell commands (Windows) in the sandbox environment.
+Run shell commands (Linux) or PowerShell commands (Windows) in the sandbox.
 
 ## Syntax
 
@@ -17,28 +17,28 @@ await testdriver.exec(language, code, timeout, silent)
 ## Parameters
 
 <ParamField path="language" type="string" required>
-  Language to execute: `'sh'` (Shell/Linux) or `'pwsh'` (PowerShell/Windows)
+  The language to run: `'sh'` (Shell/Linux) or `'pwsh'` (PowerShell/Windows)
 </ParamField>
 
 <ParamField path="code" type="string" required>
-  Code or command to execute
+  The code or the command to run
 </ParamField>
 
 <ParamField path="timeout" type="number" required>
-  Timeout in milliseconds
+  The timeout in milliseconds
 </ParamField>
 
 <ParamField path="silent" type="boolean" default="false">
-  Suppress output if `true`
+  If `true`, TestDriver does not show the output
 </ParamField>
 
 ## Returns
 
-`Promise<string>` - Command output
+`Promise<string>` - The command output
 
 ## Shell Execution (Linux)
 
-Execute shell commands in the Linux sandbox.
+Run shell commands in the Linux sandbox.
 
 ### Basic Commands
 
@@ -312,6 +312,6 @@ describe('Code Execution', () => {
 
 ## Related Methods
 
-- [`focusApplication()`](/v7/focus-application) - Focus apps before exec
-- [`find()`](/v7/find) - Locate elements visually
-- [`type()`](/v7/type) - Type text into inputs
+- [`focusApplication()`](/focus-application) - Focus apps before exec
+- [`find()`](/find) - Locate elements visually
+- [`type()`](/type) - Type text into inputs