Add integration harness and click targeting for 0.1.35-rc.3

README.md

@@ -158,12 +158,14 @@ rdt profiler export --session demo --compress
 
 - Use built-in `interact` commands before reaching for external Playwright helper scripts.
 - Current supported actions:
-  - `rdt interact click --session <name> --selector <css> [--delivery auto|playwright|dom]`
+  - `rdt interact click --session <name> (--selector <css> | --text <value> | --role <role>) [--nth <index>] [--strict] [--delivery auto|playwright|dom]`
   - `rdt interact type --session <name> --selector <css> --text <value>`
   - `rdt interact press --session <name> --key <name> [--selector <css>]`
   - `rdt interact wait --session <name> --ms <n>`
 - These commands execute through the same Playwright session that owns the current `rdt` browser page.
-- They target the first matching selector only and return structured action metadata plus trust-boundary fields.
+- `interact click` can resolve targets by CSS selector, visible text, or ARIA role.
+- `--nth` selects one match from a broader result set, and `--strict` requires exactly one match.
+- Responses now include `targetingStrategy`, `matchCount`, and `resolvedNth` alongside the delivery metadata.
 - `interact click` defaults to `--delivery auto`.
 - In `auto`, profiler-active clicks fall back to DOM dispatch and report `requestedDelivery`, `effectiveDelivery`, `profilerActive`, and `fallbackApplied`.
 - Use `--delivery playwright` to force Playwright pointer input, or `--delivery dom` to force DOM dispatch.

docs/devtools-concept-mapping.md

@@ -46,6 +46,7 @@ It is a maintenance aid for agents and contributors. It is not a commitment to r
 | `profiler compare` | `src/cli.js` | No direct public equivalent | CLI-side comparison of stored profiler artifacts or exported NDJSON files. |
 | `interact click|type|press|wait` | `src/server.js` | No direct public equivalent | Playwright-backed deterministic interaction helpers for agent workflows. |
 | `interact click --delivery` | `src/server.js` | No direct public equivalent | CLI-specific interaction contract for choosing Playwright pointer input vs DOM dispatch. |
+| `interact click --selector|--text|--role` | `src/server.js` | No direct public equivalent | Locator targeting helpers that resolve a single actionable match for CLI workflows. |
 | `session doctor` | `src/server.js` + `src/runtime-script.js` | No direct public equivalent | CLI-specific preflight that reports trust boundaries, runtime readiness, Playwright resolution diagnostics, and helper import targets. |
 
 ## Intentional Divergences

docs/workflows.md

@@ -78,13 +78,15 @@ Use it to confirm:
 Built-in interactions keep the investigation inside the same session instead of forcing separate helper scripts.
 
 ```bash
-rdt interact click --session demo --selector 'button.save' --delivery auto
+rdt interact click --session demo --role button --nth 0 --delivery auto
 rdt interact type --session demo --selector 'input[name="query"]' --text hello
 rdt interact wait --session demo --ms 500
 ```
 
 - `interact click --delivery auto` uses Playwright pointer input by default.
 - When the profiler is active, `auto` may fall back to DOM dispatch and reports the applied delivery in the response payload.
+- Use one targeting mode per click: `--selector`, `--text`, or `--role`.
+- Add `--nth` to choose one match from a broader result set, or `--strict` to require exactly one match.
 
 After interaction, verify the app settled by collecting a fresh tree or reading profiler output instead of assuming the UI state changed correctly.
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-devtool-cli",
-  "version": "0.1.35-rc.2",
+  "version": "0.1.35-rc.3",
   "description": "Agent-first CLI for React component tree inspection, snapshot-aware node debugging, and profiler analysis through a Playwright-managed browser session.",
   "license": "MIT",
   "type": "module",
@@ -37,7 +37,9 @@
     "docs:dev": "vitepress dev docs",
     "docs:preview": "vitepress preview docs --port 4173",
     "prepack": "npm run build",
-    "test": "node test/run-tests.js"
+    "test": "node test/run-tests.js",
+    "test:integration": "node scripts/run-integration-harness.mjs",
+    "test:integration:verbose": "node scripts/run-integration-harness.mjs --verbose"
   },
   "engines": {
     "node": ">=22.0.0"