devharness 0.9.14 → 0.9.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (46) hide show
  1. package/build/github/issue-body.d.ts +4 -4
  2. package/build/mcp-supervisor.js +60 -2
  3. package/build/mcp-supervisor.js.map +1 -1
  4. package/build/supervisor/client-watcher.d.ts +13 -2
  5. package/build/supervisor/client-watcher.d.ts.map +1 -1
  6. package/build/supervisor/client-watcher.js +60 -16
  7. package/build/supervisor/client-watcher.js.map +1 -1
  8. package/build/supervisor/client-watcher.test.js +110 -3
  9. package/build/supervisor/client-watcher.test.js.map +1 -1
  10. package/build/supervisor/stderr-log.d.ts +29 -0
  11. package/build/supervisor/stderr-log.d.ts.map +1 -0
  12. package/build/supervisor/stderr-log.js +52 -0
  13. package/build/supervisor/stderr-log.js.map +1 -0
  14. package/build/supervisor/stderr-log.test.d.ts +9 -0
  15. package/build/supervisor/stderr-log.test.d.ts.map +1 -0
  16. package/build/supervisor/stderr-log.test.js +80 -0
  17. package/build/supervisor/stderr-log.test.js.map +1 -0
  18. package/build/tools/issues-tools.d.ts.map +1 -1
  19. package/build/tools/issues-tools.js +29 -3
  20. package/build/tools/issues-tools.js.map +1 -1
  21. package/build/tools/issues-tools.test.js +86 -0
  22. package/build/tools/issues-tools.test.js.map +1 -1
  23. package/build/tools/replay-executor.d.ts +9 -0
  24. package/build/tools/replay-executor.d.ts.map +1 -1
  25. package/build/tools/replay-executor.js +15 -1
  26. package/build/tools/replay-executor.js.map +1 -1
  27. package/build/tools/replay-nested-rebase.test.d.ts +15 -0
  28. package/build/tools/replay-nested-rebase.test.d.ts.map +1 -0
  29. package/build/tools/replay-nested-rebase.test.js +139 -0
  30. package/build/tools/replay-nested-rebase.test.js.map +1 -0
  31. package/build/tools/replay-rebase.test.js +25 -0
  32. package/build/tools/replay-rebase.test.js.map +1 -1
  33. package/build/tools/replay-run-all-parity.test.d.ts +2 -0
  34. package/build/tools/replay-run-all-parity.test.d.ts.map +1 -0
  35. package/build/tools/replay-run-all-parity.test.js +90 -0
  36. package/build/tools/replay-run-all-parity.test.js.map +1 -0
  37. package/build/tools/replay-tools.d.ts +21 -21
  38. package/build/tools/replay-tools.d.ts.map +1 -1
  39. package/build/tools/replay-tools.js +17 -8
  40. package/build/tools/replay-tools.js.map +1 -1
  41. package/docs/instructions.md +3 -2
  42. package/docs/messages.md +3 -2
  43. package/docs/replay.md +17 -4
  44. package/package.json +1 -1
  45. package/plugin/skills/devharness/SKILL.md +1 -1
  46. package/plugin/skills/devharness/references/tool-categories.md +1 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "devharness",
3
- "version": "0.9.14",
3
+ "version": "0.9.16",
4
4
  "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",
5
5
  "type": "module",
6
6
  "main": "build/index.js",
package/plugin/skills/devharness/SKILL.md CHANGED
@@ -2,7 +2,7 @@
2
2
  name: devharness
3
3
  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.).
4
4
  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.
5
- version: 0.9.14
5
+ version: 0.9.16
6
6
  ---
7
7
 
8
8
  # devharness
package/plugin/skills/devharness/references/tool-categories.md CHANGED
@@ -65,6 +65,7 @@ runs against (see the skill's Quick Start).
65
65
 
66
66
  **Issues**: `issues` (actions: list, create, workOn, resolve, acknowledge, comment, publish, sync, import, link, pullSequence)
67
67
  - `create`/`comment`: track bugs and features as Markdown issues, optionally linked to a replay sequence
68
+ - `list`: `search` matches body and comment text. A listing holding one issue renders it in full, so `issues({ action: 'list', id: N })` returns body, labels, comments and timestamps and leaves the issue's own status and timestamps untouched - reading an issue does not need `workOn`
68
69
  - `workOn`: start on an issue, auto-replaying its linked sequence
69
70
  - **Comment as you go.** When working an issue, `comment` on it at the start (what you're about to change and why) and again when done (what you actually changed, files touched, tests added, and anything you found that contradicts the issue as written). The issue becomes the durable record - someone reviewing later reads the timeline, not your diff. Comment on surprises too: a repro that doesn't reproduce, a root cause elsewhere, or a fix you rejected and why
70
71
  - `resolve` is **human-gated**: it opens a browser overlay and only a person clicking Fixed/Not Fixed can close the issue. Don't call it unattended - it will wait ~150s and then fail with `ISSUES_RESOLVE_TIMEOUT`. Record what you found with `comment` and ask the user to run `resolve` themselves