2 Commits

Author	SHA1	Message	Date
jakevin	51bc48ec61	feat: decouple extension version from CLI version (#985) ... * feat: decouple extension version from CLI version Extension and CLI had tightly coupled version numbers (both 1.7.2), requiring manual sync across 3 files on every release. This decouples them so each can release independently. Changes: - Extension version reset to 1.0.0 with independent versioning - Extension sends compatRange (e.g. ">=1.7.0") in hello message so doctor can check CLI/extension compatibility - Daemon stores and exposes extensionCompatRange via /status - Doctor uses compatRange for compatibility checks (falls back to major-version check for older extensions without compatRange) - Doctor shows extension update availability from cached GitHub Releases data - release.yml always builds and attaches extension zip to every CLI release, so users always find both in the same release page - build-extension.yml triggers on ext-v* tags (not v*) to avoid duplicate builds * fix: version extension release assets	2026-04-13 12:43:34 +08:00
jackwener	b2fa7daf57	feat: replace @playwright/mcp with lightweight daemon + Chrome Extension ... Architecture: - Micro-daemon (HTTP + WebSocket bridge, ~190 lines, auto-start/idle-exit) - Chrome MV3 Extension using chrome.debugger CDP (10KB build) - 5 protocol actions: exec, navigate, tabs, cookies, screenshot - All DOM ops via JS evaluate — no extension update needed for new features Key features: - CDP Runtime.evaluate for JS execution in page context - Tab management, cookie access via Chrome APIs - Auto-start daemon on cold boot, idle auto-exit (5min) - Minimal permissions: debugger, tabs, cookies, activeTab, alarms Tested: zhihu hot (14.3s), twitter timeline (9.3s)	2026-03-19 16:21:17 +08:00