基线:全量源码首提(D1 版本控制落地,含第一轮优化 B1-B4/A1/A4/缩放修复)

2026-10-01 22:15:22 +08:00
commit 1e65792b09
499 changed files with 204579 additions and 0 deletions
@@ -0,0 +1,18 @@
+# Browser Interaction Troubleshooting
+
+- First use the selected browser's documented API. Do not inspect implementation source or switch control
+  mechanisms merely because a page interaction failed.
+- A stale/missing/closed tab, an empty controlled/user tab list, or an unavailable injected Playwright helper does
+  not prove the browser disconnected. Keep the existing `browser` binding. For controlled tabs, return the complete
+  `browser.tabs.list()` result in a dedicated JS call, inspect it, then call `browser.tabs.get(info.id)` in the next
+  call; if none exist, inspect `browser.user.openTabs()` and claim the matching visible page. Create a new tab only
+  when neither list contains the page. This is pre-action stale-binding recovery.
+- When an action may open a popup/new tab and the source tab does not show the expected effect, read
+  `browser.tabs.list()` and `browser.user.openTabs()` unconditionally in the same observation cell. Return
+  `{ controlledTabs, userTabs }` as that cell's final result so the model makes one decision from both lists. Do not
+  reuse the stepwise stale-binding sequence or return the controlled list first.
+- After locator timeout, strict-mode failure, or selector parse failure, take a fresh `domSnapshot()`. Rebuild a
+  unique locator from facts in that snapshot and check `count()`/`isVisible()` before acting. Do not retry the same
+  locator, guess an absent role/name/placeholder, or use `first()`/`last()`/`nth()` to hide ambiguity.
+- Only an explicit browser-disconnected error requires selecting a fresh browser and reading its effective docs
+  again. If a documented member is unavailable, use alternatives exposed by the current capability manifest.