Highlights
- Privacy-safe component inspection: strict
@refand CSS targets, explicit non-React target failures, recursive nested-secret redaction, bounded output, and an intentional--unsafe-fullescape hatch. - Trustworthy live campaigns: matched MCP/CLI task
problem-finding-v1, direct named-probe gates, distinct dashboard/docs/auth/table/canvas profiles, real canvas coverage, and nonzero exits for failed or incomplete runs. - Lower-context agent defaults: adaptive MCP perception, compact controls/reports, bounded broadcast result/error previews, and complete retry commands.
- More reliable browser orchestration:
eval --rawsurvives CLI normalization, CLI fixture servers remain responsive, andopenreadiness probes no longer create persistent tab-daemon contention. - Refreshed release surface: dependency advisories resolved, contributor/architecture docs corrected, README and GitHub Pages proof updated, and install links pinned to v2.11.0.
Measured Release Gate
- 769/769 Vitest tests passed; lint and the 81-command docs contract passed.
npm audit --audit-level=high: 0 vulnerabilities.- Final mixed live campaign: 10/10 rounds.
- Five local real-app profiles: 5/5, each 34/34 with
missingProbes: []. - Matched MCP/CLI routes: both 100%; CLI used 2,481 fewer estimated output tokens with only a 47 ms total-latency delta.
- Large-app fixture: 5,200 DOM nodes, 1,000 rows, 240 visible controls, all bounded-output coverage gates passed.
- Live Edge smoke and Playwright proof render passed; the proof page emitted zero console errors.
These real-app profiles are safe local fixtures, not claims about external production applications.
Install
Download pi-chrome-cdp-2.11.0.tgz, verify it with the attached .sha256, then extract it:
shasum -a 256 -c pi-chrome-cdp-2.11.0.tgz.sha256
mkdir -p chrome-cdp-ex-v2.11.0
tar -xzf pi-chrome-cdp-2.11.0.tgz -C chrome-cdp-ex-v2.11.0 --strip-components=1This project publishes through GitHub Releases and GitHub Pages. It is not published to the npm registry.
Full changelog: v2.10.0...v2.11.0