devharness 0.9.10 → 0.9.11

package/docs/messages.md

@@ -45,7 +45,53 @@ These templates should not be removed - they represent potential error condition
 **Type:** error
 **Code:** CHROME_LAUNCH_TIMEOUT
 
-Chrome did not become ready on port {{port}} within {{timeout}}s.
+Chrome spawned from `{{chromePath}}` and port {{port}} did not answer `/json/version` in {{probeAttempts}} probes over {{elapsedMs}}ms. No exit event was observed before the launch was abandoned.
+
+{{#probeFailures}}**Each probe's failure, in order:**
+
+```
+{{probeFailures}}
+```
+{{/probeFailures}}
+{{#stderrTail}}**Chrome stderr, last bytes:**
+
+```
+{{stderrTail}}
+```
+{{/stderrTail}}
+{{#profileDir}}**Profile retained at:** `{{profileDir}}`{{/profileDir}}
+
+---
+
+## CHROME_LAUNCH_PROCESS_EXITED
+
+**Type:** error
+**Code:** CHROME_LAUNCH_PROCESS_EXITED
+
+Chrome spawned from `{{chromePath}}` and the process ended before port {{port}} answered `/json/version`. Exit code {{exitCode}}, signal {{exitSignal}}, {{elapsedMs}}ms after spawn, across {{probeAttempts}} probes.
+
+{{#probeFailures}}**Each probe's failure, in order:**
+
+```
+{{probeFailures}}
+```
+{{/probeFailures}}
+{{#stderrTail}}**Chrome stderr, last bytes:**
+
+```
+{{stderrTail}}
+```
+{{/stderrTail}}
+{{#profileDir}}**Profile retained at:** `{{profileDir}}`{{/profileDir}}
+
+---
+
+## CHROME_BINARY_ABSENT
+
+**Type:** error
+**Code:** CHROME_BINARY_ABSENT
+
+No file exists at `{{chromePath}}`, the path resolved for platform `{{platform}}`. No process was spawned.
 
 ---
 
@@ -1220,12 +1266,6 @@ Unsupported platform: {{platform}}
 
 Failed to spawn Chrome process: {{error}}
 
-**Suggestions:**
-- Verify Chrome is installed on your system
-- Check that you have permission to execute Chrome
-- On macOS: Chrome should be at `/Applications/Google Chrome.app`
-- On Linux: Chrome/Chromium should be in your PATH
-
 ---
 
 ## PUPPETEER_NOT_CONNECTED

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devharness",
-  "version": "0.9.10",
+  "version": "0.9.11",
   "description": "MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions",
   "type": "module",
   "main": "build/index.js",

package/plugin/skills/devharness/SKILL.md

@@ -2,7 +2,7 @@
 name: devharness
 description: Drive and debug a running app via the devharness MCP server - launch or attach to Chrome and Node.js, set breakpoints and logpoints, inspect call stacks and variables, watch console and network, manage dev servers, replay any earlier tool call by its history index, and record reproduction sequences that verify a fix. Use whenever a task involves running or debugging a live app, reproducing or verifying a bug, re-driving setup you already did (relaunching, re-logging in, refilling a form), or the user mentions breakpoints, Chrome DevTools, CDP, replay sequences, or devharness tools (launchChrome, navigate, breakpoint, inspect, replay, server, issues, etc.).
 compatibility: Requires the devharness MCP server to be connected (tools such as launchChrome, breakpoint, inspect, replay, server, issues). The shell commands need `devharness` on PATH (`npm i -g devharness`); without it use `npx -y devharness@<version> <command>`. Previously published as cdp-tools-mcp.
-version: 0.9.10
+version: 0.9.11
 ---
 
 # devharness