yunti-browser-runtime 0.2.0 → 0.2.1

package/README.md

@@ -13,6 +13,13 @@ Chrome/Edge 浏览器：查看标签页、读取页面、点击输入、截图
 
 它的第一目标是：**部署简单、执行高效、和具体 Agent/平台解耦**。
 
+`0.2.1+` 默认页面操作路径优先走扩展 content script，不会自动 attach Chrome
+debugger：`yunti_observe_page`、fresh uid 的 `yunti_click` / `yunti_hover` /
+`yunti_fill` / `yunti_select` / `yunti_scroll` / `yunti_type_text` /
+`yunti_press_key` 应作为普通页面操作首选。显式 CDP、trace、部分截图 fallback、
+drag/upload/emulation/resize 和 legacy snapshot 兼容路径仍可能触发 Chrome 的调试横幅，
+只在确实需要低层能力时使用。
+
 ## 当前定位
 
 当前版本是本地单用户 MVP：
@@ -45,7 +52,8 @@ npm install -g yunti-browser-runtime
 yunti-browser-runtime print-config -- --agent codex --human
 ```
 
-把输出的 MCP 配置加入 Agent 后，加载浏览器扩展并刷新任意 `http` / `https` 页面即可。
+把输出的 MCP 配置加入 Agent 后，加载浏览器扩展并打开或保持任意 `http` / `https`
+页面即可。扩展会自动扫描可访问页面、注入内容脚本并注册到本地 bridge。
 默认不需要填写 token，不需要打开扩展 popup，也不需要保存设置。
 
 需要独立调试 bridge 时，可以手动运行：
@@ -120,11 +128,11 @@ npm run doctor:json
 6. 引导我打开 Chrome/Edge 的扩展管理页，开启开发者模式，手动加载扩展目录：
    $(npm root -g)/yunti-browser-runtime/extension
 7. 告诉我：扩展默认 bridge URL 是 http://127.0.0.1:48887，本地默认不需要 token，不需要打开 popup，也不需要保存设置。
-8. 打开任意 http/https 页面并刷新。
+8. 打开或保持任意 http/https 页面；扩展会自动尝试注入并注册已有页面。
 9. 执行：yunti-browser-runtime doctor
 10. 如果 doctor 正常，再调用 yunti_list_browser_targets 或 yunti_get_tool_usage_hints 验证你能看到浏览器页面。
 
-注意：Chrome 扩展不能由 npm 静默安装，必须由我手动在浏览器扩展页加载。扩展加载完成后默认立即可用，不要要求我填写 token、打开 popup 或保存设置；除非 doctor 明确提示 bridge 未运行，才让我单独执行 yunti-browser-runtime bridge。
+注意：Chrome 扩展不能由 npm 静默安装，必须由我手动在浏览器扩展页加载。扩展加载完成后会自动尝试接管已打开的 http/https 页面，不要默认要求我刷新页面、填写 token、打开 popup 或保存设置；只有 doctor/list targets 仍看不到页面，且确认是浏览器限制或页面未加载完成时，才把刷新目标页作为兜底。
 ```
 
 ## 安装浏览器扩展
@@ -142,7 +150,7 @@ $(npm root -g)/yunti-browser-runtime/extension
 3. 点击“加载已解压的扩展程序”。
 4. 选择本项目的 `extension/` 目录。
 5. 打开任意 `http` 或 `https` 页面。
-6. 刷新目标页面即可连接。
+6. 扩展会自动扫描并注册可访问页面；如果 doctor 仍看不到页面，再刷新目标页作为兜底。
 
 扩展默认使用 `http://127.0.0.1:48887`，本地安装不需要 token，不需要打开 popup，
 也不需要保存设置。扩展 popup 首屏只显示连接状态；自定义 bridge URL、页面匹配或
@@ -217,6 +225,8 @@ cp -R skills/yunti-browser-runtime ~/.codex/skills/
 
 - `yunti_click` / `yunti_hover` 需要 `uid`、`selector`，或同时提供 `x` 和 `y`。
 - `yunti_fill` 必须提供 `value`，并用 `uid` 或 `selector` 定位；不支持只传坐标。
+- 普通页面操作优先使用 `yunti_observe_page` 返回的 fresh uid；`0.2.1+` 的默认
+  fresh-uid action 路径不会自动 attach Chrome debugger。
 - `yunti_close_page` 按 `browserSessionId` 关闭页面；如只有 `tabId` / `targetId`，请用 `yunti_cdp_send_command` + `Target.closeTarget`。
 - `yunti_cdp_send_command` 必须提供 `method`；`params` 可选，但传入时必须是 object。
 - `yunti_forget_learning_memory` 需要 memory `id`，或使用 `all=true` 且 `confirmed=true` 删除全部。
@@ -314,10 +324,11 @@ token。
 
 ## 发布状态与后续事项
 
-- 当前稳定发布版本：`yunti-browser-runtime@0.1.3`。
-- 当前分支正在收口 `0.2.0` npm/unpacked extension 发布候选版本；`0.2.0`
-  增强了 `yunti_observe_page`、fresh uid 操作闭环、结构化恢复诊断、DOM/diagnostic
-  脱敏和可选本地控制台。
-- 发布后验证命令：`npm run release:verify-published`。
+- 当前源码版本：`yunti-browser-runtime@0.2.1`。
+- 当前已发布 npm 稳定版：`yunti-browser-runtime@0.2.0`。
+- `0.2.1` 修复默认 observe-first 页面动作误触发 Chrome debugger 的问题；
+  `0.2.0` 增强了 `yunti_observe_page`、fresh uid
+  操作闭环、结构化恢复诊断、DOM/diagnostic 脱敏和可选本地控制台。
+- `0.2.0` 发布后验证已通过：`npm run release:verify-published`。
 - 浏览器扩展商店版本不阻塞 `0.2.0` npm 发布；如要上架商店，需要沿
   `docs/EXTENSION_PERMISSION_STRATEGY.md` 另行设计 store-candidate 权限 UX。

package/docs/AGENT_WORKFLOW_CONTRACT.md

@@ -38,6 +38,17 @@ Use this loop for normal page work:
 - Coordinates/selectors: use them as recovery or debugging paths when fresh
   uids are unavailable.
 
+## Debugger Boundary
+
+- In `0.2.1+`, normal observe-first page actions should not automatically
+  attach Chrome debugger. Prefer `yunti_observe_page` plus fresh uid
+  `yunti_click`, `yunti_hover`, `yunti_fill`, `yunti_select`, `yunti_scroll`,
+  `yunti_type_text`, and `yunti_press_key` on anti-debug-sensitive pages.
+- Chrome debugger banners may still appear for explicit low-level or advanced
+  tools such as `yunti_cdp_send_command`, raw CDP diagnostics, performance
+  tracing, screenshot fallback paths, drag, upload, emulation, resize, or
+  legacy snapshot compatibility.
+
 ## Confirmation Boundary
 
 Ask the user for explicit confirmation before:

package/docs/EXECUTION_PLAN.md

@@ -82,7 +82,7 @@
 | P6.6.2 | 已完成 | 商店权限与隐私文案草案 |
 | P6.6.3 | 已完成 | 商店前权限策略决策 |
 | P6.6.4 | 后置 | Store candidate 权限 UX 设计 |
-| P7.1 | 进行中 | 0.2.0 npm/unpacked 发布收口 |
+| P7.1 | 已完成 | 0.2.0 npm/unpacked 发布收口 |
 
 当前 0.2.0 推进快照（2026-07-05）：
 
@@ -2691,7 +2691,7 @@ P6.6.4 后置：
 
 ## P7.1 0.2.0 npm/unpacked 发布收口
 
-状态：进行中
+状态：已完成
 
 目标：
 
@@ -2700,32 +2700,31 @@ P6.6.4 后置：
 完成范围：
 
 - package 和 extension 版本同步提升到 `0.2.0`。
-- README / Release / status / execution plan 更新为 0.2.0 release candidate。
-- 执行 `npm run check:metadata`、`npm run release:prepublish`、真实浏览器 E2E 和
-  `npm run release:dry-run`。
-- 不在本切片执行 `npm run release:publish`，除非用户明确要求发布。
+- README / Release / status / execution plan 先更新为 0.2.0 发布候选状态，并在发布后
+  更新为已发布状态。
+- 执行 `npm run check:metadata`、`npm run release:prepublish`、真实浏览器 E2E、
+  `npm run release:dry-run`、`npm run release:publish` 和
+  `npm run release:verify-published`。
 
 当前验证：
 
 - `git diff --check` 通过。
 - token 残留检查无输出。
-- `npm run check:metadata` 曾通过，确认 GitHub repository/homepage/bugs URL 为 200，
-  npm registry 当前已发布版本为 `0.1.3`；随后同一检查因当前环境访问 GitHub 超时而失败。
-- `npm run release:check` 通过，包含 public documentation residue check、17 个公开
+- `npm run check:metadata` 通过，确认 GitHub repository/homepage/bugs URL 为 200。
+- `npm run release:check` 通过，包含 public documentation residue check、18 个公开
   Markdown 文件链接检查、version consistency check `0.2.0`、CLI smoke `0.2.0`、
-  action result coverage 11 行、npm package 内容 48 个文件和 extension zip 内容 13 个文件。
+  action result coverage 11 行、npm package 内容 49 个文件和 extension zip 内容 13 个文件。
 - `YUNTI_E2E=1 npm run test:e2e` 在本机 `pytest-playwright` 环境下通过 1 个真实浏览器
   extension bridge smoke；conda 仅打印 requests 依赖版本 warning，不影响结果。
-- `npm publish --dry-run --registry=https://registry.npmjs.org/` 通过，生成
-  `yunti-browser-runtime-0.2.0.tgz` dry-run 预览，tarball 共 48 个文件。
-- `npm run release:prepublish` 和 `npm run release:dry-run` 当前仍受
-  `check:metadata` 的 GitHub 请求超时影响，需要网络恢复后重跑。
+- `npm run release:dry-run` 通过，生成 `yunti-browser-runtime-0.2.0.tgz` dry-run
+  预览，tarball 共 49 个文件。
+- `npm run release:publish` 已发布 `yunti-browser-runtime@0.2.0` 到官方 npm registry。
+- `npm run release:verify-published` 已验证 name、version、repository、homepage、bugs
+  和 tarball URL。
 
 下一步：
 
-- 网络恢复后重跑 `npm run check:metadata`、`npm run release:prepublish` 和
-  `npm run release:dry-run`。
-- 上述脚本门禁全部通过后，由用户确认是否执行正式 npm publish。
+- 选择 post-0.2 下一阶段；P6.6.4 store-candidate 权限 UX 仍作为浏览器商店方向后置。
 
 详细范围、非目标和验收标准见 `docs/NEXT_MAJOR_PLAN.md`。
 
@@ -2768,8 +2767,43 @@ rg "/U[s]ers|C[o]deg|x[y]y|y[b]m100" README.md docs skills package.json
 
 ## 当前下一步
 
-P0.1-P6.0 已完成，`yunti-browser-runtime@0.1.3` 已发布到官方 npm registry。
-当前分支正在收口 `0.2.0` npm/unpacked release candidate。
+P0.1-P7.1 已完成，`yunti-browser-runtime@0.2.0` 已发布到官方 npm registry。
+
+## P7.2 0.2.1 安装后自动注入 / 自动注册页面
+
+状态：实施中，代码与文档已完成，等待完整验证和提交。
+
+目标：
+
+让用户加载扩展后尽量不需要手动刷新页面。扩展后台应主动扫描可访问的 `http` /
+`https` tabs，对没有注册 session 的页面注入 `dom-observer.js`、`content.js` 和
+`content.css`，再触发 `yunti_refresh_registration`，使 Agent 能直接发现和操作已打开页面。
+bridge 重启或 background service worker 恢复后，也应尽量自动恢复注册。
+
+非目标：
+
+- 不绕过 Chrome 对 `chrome://`、扩展页、Web Store、权限不足页面等不可注入页面的限制。
+- 不引入远程服务、不要求用户填写 token、不要求默认打开 popup。
+- 不改变普通 observe-first action 的非 CDP 默认路径。
+
+验收：
+
+- manifest 增加必要的 `scripting` 能力。
+- background/session manager 支持 scan -> ping -> inject -> refresh registration。
+- 安装/startup、tab update/activation、popup refresh、targets inventory/recovery 等路径能触发恢复。
+- README / INSTALL / skill / Tool Guide / usage hints / doctor guidance 不再默认要求用户刷新；
+  只把刷新作为无法注入时的兜底恢复。
+- `git diff --check`、token 残留检查、`npm run release:check` 通过；涉及真实浏览器链路时执行
+  `YUNTI_E2E=1 npm run test:e2e`。
+
+进展：
+
+- manifest 已新增 `scripting` 权限，用于向已打开的受支持页面注入打包内容脚本。
+- session manager 已支持 scan -> ping -> inject -> refresh registration，并带同页短时间去重。
+- background 已接入 install/startup/background start、tab activated、tab updated complete。
+- popup refresh 和 `yunti_list_browser_targets` 已接入自动恢复。
+- README、INSTALL、doctor、console guidance、skill、store/permission docs 已改为自动注册优先，
+  刷新页面只作为浏览器限制下的兜底。
 
 - 发布后验证已通过：`npm run release:verify-published`。
 - 本地默认使用不再需要 bridge token；需要加固时可显式设置
@@ -2783,7 +2817,7 @@ P0.1-P6.0 已完成，`yunti-browser-runtime@0.1.3` 已发布到官方 npm regis
   P6.5.2 控制台诊断增强第一刀已完成，P6.5.3 控制台真实浏览器 E2E 验收已完成，
   P6.6.1 浏览器扩展分发准备已完成，P6.6.2 商店权限与隐私文案草案已完成，
   P6.6.3 商店前权限策略决策已完成。P6.6.4 Store candidate 权限 UX 设计已后置；
-  当前进入 P7.1 0.2.0 npm/unpacked 发布收口。
+  P7.1 0.2.0 npm/unpacked 发布收口已完成。
 - 保持兼容：不改变成功 fill、select、scroll、CDP、截图、network/console、file upload 或 tab
   能力；新增诊断只在失败结果或 observe 元数据里追加更具体的 `code`、`recoveryHint`、
   `element` / 字段状态摘要和验证提示。

package/docs/EXTENSION_DISTRIBUTION.md

@@ -56,6 +56,7 @@ Current file: `extension/manifest.json`.
 | `manifest_version` | `3` | Required modern extension format. | Low. | Keep. |
 | `permissions.activeTab` | present | Visible-tab capture fallback and temporary page access semantics. | Low to medium; generally narrower than persistent host access. | Keep. |
 | `permissions.debugger` | present | CDP commands, target-level automation, console/runtime/network events, and low-level recovery. | High. Chrome shows a debugger warning and reviewers may ask why this is core. | Keep for now; store copy must explain this is the core browser automation transport. |
+| `permissions.scripting` | present | Programmatically inject packaged content scripts into already-open supported pages after extension load or recovery. | Medium with broad host access; reviewers may ask why dynamic injection is needed. | Keep for developer/npm path so install does not require manual page refresh; explain it as recovery/registration, not arbitrary remote code execution. |
 | `permissions.storage` | present | Local bridge URL, optional token, user id/name, and page match settings. | Low. | Keep. |
 | `permissions.tabs` | present | Tab inventory, active tab selection, switching, and metadata routing. | Medium. Chrome may warn about browsing history. | Keep for now; evaluate whether any read paths can use host/activeTab data later. |
 | `permissions.webRequest` | present | Sanitized network diagnostics and request observation. | Medium to high with broad hosts. | Keep for now; P6.6.2 should evaluate optionalizing network diagnostics. |

package/docs/EXTENSION_PERMISSION_STRATEGY.md

@@ -12,7 +12,7 @@ current `0.2.0` development cycle:
 - broad `http` / `https` host access remains acceptable for the local developer
   and npm-installed extension path;
 - `webRequest` remains available by default for local diagnostics;
-- `debugger`, `tabs`, screenshots, CDP, network, console, upload, and tab
+- `debugger`, `scripting`, `tabs`, screenshots, CDP, network, console, upload, and tab
   capabilities remain part of Yunti's core local browser automation surface;
 - the current manifest should not be submitted to Chrome Web Store or Edge
   Add-ons as the recommended store build without an explicit maintainer
@@ -47,7 +47,7 @@ developer install:
 - Edge policy says extensions should request only permissions essential for the
   declared functionality, and must clearly disclose dependency on non-integrated
   software and testing steps.
-- Yunti's current `debugger`, broad host access, `tabs`, and `webRequest`
+- Yunti's current `debugger`, `scripting`, broad host access, `tabs`, and `webRequest`
   combination is truthful for a browser automation runtime, but it is also the
   highest-review-burden shape.
 
@@ -74,9 +74,11 @@ The safest product path is therefore:
 
 Keep current behavior:
 
-- `permissions`: `activeTab`, `debugger`, `storage`, `tabs`, `webRequest`.
+- `permissions`: `activeTab`, `debugger`, `scripting`, `storage`, `tabs`, `webRequest`.
 - `host_permissions`: `http://*/*`, `https://*/*`, localhost bridge access.
 - Static content scripts for `http` / `https` pages.
+- Programmatic injection for already-open supported pages after extension load,
+  startup, bridge recovery, or target inventory refresh.
 - Popup remains zero-config by default.
 - Advanced page match patterns remain a runtime registration filter, not a
   browser permission boundary.
@@ -113,9 +115,10 @@ Before any store build with narrowed permissions:
   when the current page is blocked by missing host permission.
 - Agent-facing errors should say whether the page is unavailable because host
   permission is missing, the bridge is offline, the page is unsupported, or the
-  extension needs a refresh.
+  browser blocked automatic injection.
 - Tool hints and the packaged skill should explain how to recover:
-  `open page -> grant site access -> refresh -> yunti_list_browser_targets`.
+  `open page -> grant site access -> yunti_list_browser_targets`, with page
+  refresh only as a fallback.
 - Optional network diagnostics should be visibly separate from basic DOM
   automation.
 - `doctor` should detect permission-mode problems and provide a human-readable
@@ -136,7 +139,7 @@ small and testable:
 6. Add real-browser E2E coverage for:
    - page blocked before host grant;
    - grant access;
-   - refresh/register;
+   - auto-register existing pages;
    - observe/action success;
    - optional diagnostics enabled/disabled.
 7. Update store copy and privacy text after the final manifest strategy is

package/docs/EXTENSION_STORE_COPY.md

@@ -84,6 +84,7 @@ Edge certification notes, and any public privacy-policy explanation.
 | --- | --- | --- | --- |
 | `activeTab` | Allows temporary access to the visible tab for user-directed capture and fallback operations. | Used as a narrower visible-tab fallback where possible. It does not replace persistent access needed for the current automation workflow. | Keep. |
 | `debugger` | Enables the local agent to control the user's browser tab through the browser's debugging protocol. | Core transport for CDP commands, target routing, console/runtime diagnostics, screenshots, and low-level recovery. This is high-sensitivity and must be explained as the product's primary browser automation mechanism. | Keep for current developer path; re-review before store submission. |
+| `scripting` | Lets the extension inject its packaged content scripts into supported pages that were already open before the extension loaded. | Used for automatic page registration and recovery after install, browser startup, or background service worker restart. It does not execute remote code. | Keep for current developer path so users do not need to refresh pages by default; re-review before store submission. |
 | `storage` | Saves local extension settings such as bridge URL, optional token, user id/name, and page match settings. | Stores local configuration only. It is not used for hosted sync by default. | Keep. |
 | `tabs` | Lets the agent list and switch the user's open browser tabs. | Needed for tab inventory, target selection, activation, and routing metadata. Store copy should explain that tab metadata is used only for user-directed local automation. | Keep for current workflow; evaluate narrower alternatives later. |
 | `webRequest` | Lets the runtime provide sanitized network diagnostics when debugging page automation. | Used for observation and diagnostics, not ad blocking or request modification. Because this combines with broad hosts, consider making network diagnostics optional in a later slice. | Keep for developer path; P6.6.3 should decide optionalization. |
@@ -151,7 +152,9 @@ include install and test steps:
 2. Install the runtime package.
 3. Start or configure an MCP-capable agent so it launches the local bridge.
 4. Install the extension build.
-5. Open and refresh an `http` or `https` page.
+5. Open or keep an `http` or `https` page; the extension auto-registers
+   accessible pages and only needs a refresh if browser restrictions prevent
+   injection.
 6. Run `yunti-browser-runtime doctor`.
 7. Verify that the extension shows a connected page and that MCP tools can list
    browser targets.

package/docs/INSTALL.md

@@ -63,7 +63,8 @@ Development loading:
 2. Enable developer mode.
 3. Choose "Load unpacked".
 4. Select the project `extension/` directory.
-5. Open or refresh any `http` or `https` page.
+5. Open or keep any `http` or `https` page. The extension automatically tries
+   to inject and register accessible existing pages.
 6. Do not open the extension popup unless you want to confirm status or
    customize settings.
 
@@ -150,8 +151,9 @@ npm run print-config -- --agent cline --human
 ```
 
 Add the printed server entry to Cline's MCP settings. Keep the extension loaded
-in Chrome/Edge and refresh the target page so the content script registers a
-fresh `browserSessionId`.
+in Chrome/Edge. The extension should register accessible `http`/`https` pages
+automatically; refresh the target page only if browser restrictions or a failed
+doctor check make it necessary.
 
 ## Check Health
 
@@ -187,7 +189,9 @@ runs the unit test suite, and verifies the npm package contents with
 
 ## Common Recovery
 
-- If tools say no browser tab is connected, refresh the target page.
+- If tools say no browser tab is connected, call `yunti_list_browser_targets`
+  or run doctor first; the extension will try to auto-register accessible pages.
+  Refresh the target page only as a fallback.
 - If doctor reports `authorized: false` with `authRequired: true`, set
   `YUNTI_BROWSER_BRIDGE_TOKEN` and save the same token in the extension popup.
 - If an old `browserSessionId` fails, call `yunti_list_browser_targets` again
@@ -198,8 +202,9 @@ runs the unit test suite, and verifies the npm package contents with
   is rejected.
 - For closing a raw `tabId` or `targetId`, use `yunti_cdp_send_command` with
   `Target.closeTarget` instead of `yunti_close_page`.
-- If the extension was reloaded, refresh browser pages so the content script can
-  register again.
+- If the extension was reloaded, it should scan and register accessible pages
+  automatically. Refresh browser pages only if the page cannot be injected or
+  remains invisible after the recovery check.
 
 ## Real Browser Smoke Test
 

package/docs/NEXT_MAJOR_PLAN.md

@@ -1,7 +1,7 @@
 # Next Major Plan: 0.2.0 Best Browser Automation Runtime
 
-This document is the durable planning contract for the next major development
-cycle after `yunti-browser-runtime@0.1.3`.
+This document is the durable planning contract for the `0.2.0` development
+cycle, now completed by `yunti-browser-runtime@0.2.0`.
 
 ## Goal
 
@@ -708,14 +708,14 @@ P6.6.4 deferred:
 
 ### P7.1 0.2.0 Release Closure
 
-Status: in progress.
+Status: completed.
 
 Scope:
 
 - bump package and extension versions to `0.2.0`;
 - preserve the npm/unpacked developer path and current local runtime behavior;
-- run metadata, release, real-browser E2E, and dry-run gates;
-- ask for explicit user confirmation before formal npm publish.
+- run metadata, release, real-browser E2E, dry-run, publish, and
+  post-publish verification gates.
 
 ## Suggested Implementation Order
 

package/docs/PROJECT_STATUS.md

@@ -2,17 +2,49 @@
 
 ## Current Phase
 
-Patch release `yunti-browser-runtime@0.1.3` is complete. The project is now
-closing the `0.2.0 Best Browser Automation Runtime` npm/unpacked release
-candidate, documented in `docs/NEXT_MAJOR_PLAN.md`.
+Release `yunti-browser-runtime@0.2.0` is complete and verified on the official
+npm registry. The current patch line is `0.2.1`, focused on making default
+observe-first page actions avoid automatic Chrome debugger attachment.
 
-Current implementation focus: P7.1 `0.2.0` npm/unpacked release closure.
+Current implementation focus: `0.2.1` install/bridge recovery without default
+manual page refresh. The anti-debug-sensitive default action path is already in
+place: fresh-uid `yunti_click`, `yunti_hover`, `yunti_fill`, `yunti_select`,
+`yunti_type_text`, and `yunti_press_key` dispatch through content script page
+events instead of CDP mouse/keyboard/runtime commands. Explicit CDP, trace,
+screenshot fallback, drag/upload/emulation/resize, and legacy snapshot
+compatibility remain low-level/advanced paths that may show the Chrome debugger
+banner.
+
+Post-0.2 planning remains active after this patch.
 P6.6.1 browser extension distribution readiness, P6.6.2 store-facing
 permission/privacy copy, and P6.6.3 pre-store permission strategy decision are
 complete; P6.5 optional local runtime console is complete through real-browser
 validation. P6.6.4 store-candidate permission UX design is deferred to the
 post-0.2 store-candidate track.
 
+Active slice status: `0.2.1` install/bridge recovery has code and docs in
+progress. The extension background scans accessible `http` / `https` tabs after
+install/startup/background recovery, tab activation/update, popup refresh, and
+`yunti_list_browser_targets`; it pings existing content scripts, injects the
+packaged scripts when missing, and triggers registration automatically. Manual
+refresh is now documented as a last resort only for pages Chrome cannot inject
+into, unsupported protocols, missing permissions, or other browser-enforced
+limits.
+
+Acceptance for this slice:
+
+- Add `scripting`-based auto injection / auto registration for existing
+  supported tabs.
+- Trigger recovery on extension install/startup, tab activation/update, popup
+  refresh, and list-targets style inventory recovery where feasible.
+- Keep the content-script observe/action path non-CDP by default.
+- Update README, install guide, skill, Tool Guide, and usage hints so agents no
+  longer tell users to refresh as the default post-install step.
+- Doctor/no-session guidance should prefer automatic recovery and mention manual
+  refresh only as a fallback.
+- Verify with unit tests, release checks, and real-browser E2E if browser
+  behavior changes.
+
 Latest visible 0.2.0 phase split:
 
 - P6.1.1 completed: `yunti_observe_page` schema, tool hints, and bridge
@@ -77,7 +109,7 @@ Latest visible 0.2.0 phase split:
 - P6.6.2 completed: store-facing permission and privacy copy.
 - P6.6.3 completed: pre-store permission strategy decision.
 - P6.6.4 deferred: store-candidate permission UX design.
-- P7.1 in progress: `0.2.0` npm/unpacked release closure.
+- P7.1 completed: `0.2.0` npm/unpacked release closure and npm publication.
 
 Latest detailed P6.2 status:
 
@@ -315,18 +347,11 @@ Latest detailed P6.2 status:
   public documentation residue checks, public Markdown link checks for 17 files,
   11 action-result coverage rows, npm package contents validation with 48
   files, and extension zip contents validation with 13 files.
-- Next: complete P7.1 `0.2.0` npm/unpacked release closure. Version has moved
-  to `0.2.0`; run metadata, release, real-browser E2E, and dry-run gates before
-  asking for confirmation to publish. P6.6.4 store-candidate permission UX is
-  intentionally deferred and should not block this npm/unpacked release.
-- P7.1 current validation: package and extension versions are both `0.2.0`;
-  `git diff --check`, token residue grep, `npm run release:check`,
-  `YUNTI_E2E=1 npm run test:e2e`, and direct
-  `npm publish --dry-run --registry=https://registry.npmjs.org/` passed.
-  `npm run check:metadata` passed once for the public GitHub/npm metadata, then
-  later failed because this environment timed out connecting to GitHub; scripted
-  `release:prepublish` and `release:dry-run` need to be rerun when GitHub is
-  reachable again.
+- P7.1 completed: package and extension versions are both `0.2.0`; metadata,
+  release, dry-run, publish, and post-publish verification gates passed.
+  `npm run release:publish` published `yunti-browser-runtime@0.2.0` to the
+  official npm registry, and `npm run release:verify-published` verified the
+  published package metadata and tarball URL.
 
 ## Current State
 
@@ -364,9 +389,7 @@ Latest detailed P6.2 status:
 - `npm run release:dry-run` and `npm run release:publish` pin the official npm
   registry at `https://registry.npmjs.org/`, avoiding accidental publication to
   a locally configured mirror registry.
-- `yunti-browser-runtime@0.1.3` is published on the official npm registry.
-- Current branch package and extension versions are being prepared as
-  `0.2.0` release candidate.
+- `yunti-browser-runtime@0.2.0` is published on the official npm registry.
 - Extension popup is a zero-config status panel by default; Bridge URL, page
   matching, and optional Bridge Token stay under advanced settings.
 - `npm run test:e2e` provides an opt-in real-browser Playwright smoke test for
@@ -1102,8 +1125,9 @@ Latest detailed P6.2 status:
   real-browser console validation. P6.6.1 browser extension distribution
   readiness, P6.6.2 store-facing permission/privacy copy, and P6.6.3 pre-store
   permission strategy decision are complete. P6.6.4 store-candidate permission
-  UX design is deferred to post-0.2. The next anchored slice is P7.1 `0.2.0`
-  npm/unpacked release closure.
+  UX design is deferred to post-0.2. The next anchored slice should be chosen
+  from post-0.2 planning, with browser-store permission UX still available as a
+  separate store-candidate track.
 - For the next coding slice, update all affected guidance surfaces in one
   commit: `mcp/tools.js`, `docs/TOOL_GUIDE.md`,
   `skills/yunti-browser-runtime/SKILL.md`, `docs/EXECUTION_PLAN.md`, and this

package/docs/RELEASE_0_2_0_CHECKLIST.md

@@ -101,7 +101,9 @@ Yunti 继续坚持自己的特色：
 
 - popup 首屏是零配置状态面板；
 - bridge URL、page match、optional token 放入高级设置；
-- 默认加载扩展、刷新任意 `http` / `https` 页面即可连接；
+- `0.2.0` 默认加载扩展、刷新任意 `http` / `https` 页面即可连接；
+- `0.2.1` 进一步改进为加载扩展后自动扫描、注入并注册可访问的已打开页面，
+  刷新页面只作为浏览器限制下的兜底；
 - 不需要打开 popup、不需要保存设置、不需要填 token；
 - popup 仍可用于高级调试和自定义配置。
 
@@ -641,7 +643,7 @@ http://127.0.0.1:48887/console
 - store-candidate manifest；
 - 商店权限相关测试。
 
-当前发布目标是 npm/unpacked release candidate，而不是浏览器商店提交版。
+0.2.0 发布目标是 npm/unpacked release，而不是浏览器商店提交版。
 
 ## 发布门禁增强
 
@@ -775,14 +777,14 @@ http://127.0.0.1:48887/console
 
 这些边界是主动选择。当前重点是把 Yunti 做成可靠的本地浏览器操作层。
 
-## 发布前清单
+## 发布前后清单
 
 正式发布 `0.2.0` 前确认：
 
 - 工作区干净；
 - `package.json` 是 `0.2.0`；
 - `extension/manifest.json` 是 `0.2.0`；
-- README 在发布前仍说明稳定版为 `0.1.3`，发布后再改成 `0.2.0`；
+- README 发布前仍说明稳定版为 `0.1.3`，发布后改成 `0.2.0`；
 - browser store 工作明确为 post-0.2；
 - public files 没有 npm/GitHub 凭据或 registry auth 配置片段；
 - `npm run check:metadata` 通过；
@@ -803,7 +805,12 @@ npm run release:publish
 npm run release:verify-published
 ```
 
-发布后还需要把 README 和状态文档从 release candidate 更新为已经发布的 `0.2.0`。
+发布结果：
+
+- `npm run release:publish` 已发布 `yunti-browser-runtime@0.2.0`；
+- `npm run release:verify-published` 已验证 name、version、repository、homepage、bugs
+  和 tarball URL；
+- README 和状态文档已从发布候选状态更新为已经发布的 `0.2.0`。
 
 ## 对外 changelog 短版
 

package/docs/TOOL_GUIDE.md

@@ -143,6 +143,14 @@ taking an action whose effect cannot be verified from page state.
 
 ## CDP Rules
 
+- In `0.2.1+`, normal observe-first page actions should not automatically
+  attach Chrome debugger. Prefer `yunti_observe_page` plus fresh uid
+  `yunti_click`, `yunti_hover`, `yunti_fill`, `yunti_select`, `yunti_scroll`,
+  `yunti_type_text`, and `yunti_press_key` on anti-debug-sensitive pages.
+- Chrome debugger banners may still appear for explicit low-level or advanced
+  tools such as `yunti_cdp_send_command`, raw CDP diagnostics, performance
+  tracing, screenshot fallback paths, drag, upload, emulation, resize, or
+  legacy snapshot compatibility.
 - Do not run CDP method names in a shell.
 - Use `yunti_cdp_send_command` with `method` and optional `params`.
 - `params` must be an object when provided.

package/extension/background.js

@@ -18,6 +18,7 @@ const cdp = createCdpController({
   postBridge,
   startPolling,
   forwardConsoleEvent,
+  ensureAllTabsRegistered: sessionManager.ensureAllTabsRegistered,
 })
 
 const { detachCdpTab, installCdpEventForwarder } = cdp
@@ -45,6 +46,23 @@ chrome.tabs.onRemoved.addListener((tabId) => {
 
 chrome.tabs.onActivated.addListener(({ tabId }) => {
   void sessionManager.activateTab(tabId)
+  void sessionManager.ensureTabRegistered(tabId, { reason: "tab_activated" }).catch(() => {})
+})
+
+chrome.tabs.onUpdated.addListener((tabId, changeInfo, tab) => {
+  if (changeInfo.status !== "complete") return
+  void sessionManager.ensureTabRegistered(tabId, {
+    tab,
+    reason: "tab_updated_complete",
+  }).catch(() => {})
+})
+
+chrome.runtime.onInstalled.addListener(() => {
+  void sessionManager.ensureAllTabsRegistered({ reason: "extension_installed" }).catch(() => {})
+})
+
+chrome.runtime.onStartup.addListener(() => {
+  void sessionManager.ensureAllTabsRegistered({ reason: "browser_startup" }).catch(() => {})
 })
 
 chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
@@ -53,3 +71,5 @@ chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
   )
   return true
 })
+
+void sessionManager.ensureAllTabsRegistered({ reason: "background_started" }).catch(() => {})

package/extension/cdp.js

@@ -4,6 +4,7 @@ export function createCdpController({
   postBridge,
   startPolling,
   forwardConsoleEvent,
+  ensureAllTabsRegistered,
 }) {
   const cdpAttachedTabs = new Set()
   const cdpEnabledDomains = new Map()
@@ -159,6 +160,9 @@ export function createCdpController({
   }
 
   async function listBrowserTargets(session) {
+    if (typeof ensureAllTabsRegistered === "function") {
+      await ensureAllTabsRegistered({ reason: "list_browser_targets" }).catch(() => null)
+    }
     const cdpResult = await interceptTargetGetTargets(session)
     const targetInfos = Array.isArray(cdpResult?.result?.targetInfos)
       ? cdpResult.result.targetInfos