v2.17.0

v2.17.0 ships the live-path shrink (#375 / #389): the operator card is 20
survivors; Board 2 ten jobs 0 FAIL. README front door is live-session
attach, not the 10/8/9 PK scoreboard SVG. Daily Chrome 136 / Electron
CDP_PORT=9333 honesty stays. The competitor board remains in
docs/pk-324-board.md.

Agent reliability

• Unprefixed doctor no longer treats an empty 9222 — or a leftover isolated
  chrome-cdp-ex-* occupant on 9222 — as the next step when a live tab
  daemon is already attached (Electron on CDP_PORT=9333 and similar).
  Doctor acknowledges that session and recommends
  CDP_PORT=<port> cdp doctor / cdp list instead of
  spawn-debug-browser ... --port 9222. Isolated leftover 9222 with no
  daemon is still not daily attach; empty 9222 with no daemon still
  recommends the persistent daily dir (#372).

• --daily-profile treats Chromium Opening in existing browser session /
  在現有的瀏覽器工作階段中開啟 as failure, not attach success. Chrome 136+
  / Edge ignore --remote-debugging-port on the default user-data-dir, so
  --daily-profile does not quit+relaunch that same default profile as if
  CDP would appear. Isolated spawn (non-default --user-data-dir) remains
  fallback only and is not the daily profile; logged-in cookies will not
  transfer. Doctor empty 9222 on a 136+ preferred browser recommends that
  isolated fallback instead of doomed daily default-dir debug (#366).

• Empty 9222 recommends --daily-profile for doctor's preferredBrowser
  (macOS default HTTP handler when Edge/Chrome/Brave; not hardcoded
  chrome or edge), ask first. Isolated tmp spawn stays fallback and is
  not the daily profile. spawn-debug-browser --help / unknown flags
  print help and do not launch a browser (#364).

• Leftover isolated chrome-cdp-ex-* debug Chrome on 9222 is not daily
  attach success. Doctor/list recommend --daily-profile (ask first)
  and do not kill the occupant. Explicit CDP_PORT still attaches.
  Live daily debug on 9222 stays success (#362).

• When 9222 is empty, doctor recommends enabling debug on the daily Chrome
  profile (spawn-debug-browser --daily-profile) before isolated spawn.
  Isolated spawn remains fallback only and is not the daily profile.
  Occupied live 9222 stays attach success (#360).

fix: stop first-step doctor/spawn loop when CDP is already up

• Stop the first-step doctor/spawn loop when Chrome is already listening on
  9222. Unprefixed doctor/list/perceive probe the spawn default port,
  a live occupant is attach success (CDP_PORT + cdp list), isolated spawn
  is fallback only and is not the daily profile, and doctor prints
  preferredBrowser instead of hardcoded Edge (#358).

fix(infra): probe 127.0.0.1:9224 when DevToolsActivePort is missing

• list / doctor still try CDP_PORT then DevToolsActivePort. When both
  miss, they probe http://127.0.0.1:9224/json/version on the same path as
  CDP_PORT=9224 (including the HTTP 404 → /devtools/browser fallback).
  Chrome 136+ often does not write that file. A closed 9224 stays an
  environment miss; do not spawn a new profile.

docs: draw the README PK scoreboard as SVG

• README comparison first glance is a generated scoreboard SVG (PASS/FAIL
  plus steps / token / wall ms). The markdown grid stays in
  docs/pk-324-board.md. Install stays pinned to published v2.16.0.

docs: make README comparison a horizontal PK table

• README comparison is a horizontal success PK table (chrome-cdp-ex 10/10,
  Browser Use 8/10, Playwright 9/10) with PDF and overlay FAIL visible.
  Steps / token / time bar charts sit below the table. The engineer grid
  stays in docs/pk-324-board.md. Install stays pinned to published v2.16.0.

Package

• Asset: pi-chrome-cdp-2.17.0.tgz
• SHA-256: cf56532b1fdf08909707a66a39723aeaae55d7aa2e370fdb549bb389db40c09a
• Includes cross-host manifests, validation scripts, Codex Killer Path evidence, demo media, CLI shim, setup script, and skills runtime.