@omniaibot/win-x64 1.6.6 → 1.6.7

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/css-only-dropdown-js.md

@@ -1,50 +1,50 @@
-# CSS-Only Dropdown JavaScript Recipe
-
-Use only after semantic find, refs, selectors, DOM, and mouse fallback cannot expose or select the dropdown option.
-
-Example for a visible trigger like `按留言时间排序` and a target option text:
-
-```js
-const triggerText = '按留言时间排序';
-const optionText = '目标选项文本';
-
-const visibleElements = [...document.querySelectorAll('button, [role="button"], [aria-haspopup], div, span, li')]
-  .filter((el) => {
-    const style = getComputedStyle(el);
-    const box = el.getBoundingClientRect();
-    return style.display !== 'none' && style.visibility !== 'hidden' && box.width > 0 && box.height > 0;
-  });
-
-const byExactText = (text) => visibleElements.find((el) => el.textContent?.trim() === text);
-const trigger = byExactText(triggerText);
-if (!trigger) {
-  return { ok: false, reason: 'trigger-not-found', triggerText, optionText };
-}
-
-trigger.click();
-await new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)));
-
-const option = [...document.querySelectorAll('div, span, li, button, [role="option"], [role="menuitem"]')]
-  .filter((el) => {
-    const style = getComputedStyle(el);
-    const box = el.getBoundingClientRect();
-    return style.display !== 'none' && style.visibility !== 'hidden' && box.width > 0 && box.height > 0;
-  })
-  .find((el) => el.textContent?.trim() === optionText);
-
-if (!option) {
-  return { ok: false, reason: 'option-not-found-after-trigger-click', triggerText, optionText };
-}
-
-option.click();
-await new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)));
-
-return {
-  ok: true,
-  triggerText,
-  optionText,
-  selectedText: trigger.textContent?.trim(),
-};
-```
-
-Verify with page state after running the script: selected label, sorted result order, result count, URL/query state, or another user-visible condition.
+# CSS-Only Dropdown JavaScript Recipe
+
+Use only after semantic find, refs, selectors, DOM, and mouse fallback cannot expose or select the dropdown option.
+
+Example for a visible trigger like `按留言时间排序` and a target option text:
+
+```js
+const triggerText = '按留言时间排序';
+const optionText = '目标选项文本';
+
+const visibleElements = [...document.querySelectorAll('button, [role="button"], [aria-haspopup], div, span, li')]
+  .filter((el) => {
+    const style = getComputedStyle(el);
+    const box = el.getBoundingClientRect();
+    return style.display !== 'none' && style.visibility !== 'hidden' && box.width > 0 && box.height > 0;
+  });
+
+const byExactText = (text) => visibleElements.find((el) => el.textContent?.trim() === text);
+const trigger = byExactText(triggerText);
+if (!trigger) {
+  return { ok: false, reason: 'trigger-not-found', triggerText, optionText };
+}
+
+trigger.click();
+await new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)));
+
+const option = [...document.querySelectorAll('div, span, li, button, [role="option"], [role="menuitem"]')]
+  .filter((el) => {
+    const style = getComputedStyle(el);
+    const box = el.getBoundingClientRect();
+    return style.display !== 'none' && style.visibility !== 'hidden' && box.width > 0 && box.height > 0;
+  })
+  .find((el) => el.textContent?.trim() === optionText);
+
+if (!option) {
+  return { ok: false, reason: 'option-not-found-after-trigger-click', triggerText, optionText };
+}
+
+option.click();
+await new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)));
+
+return {
+  ok: true,
+  triggerText,
+  optionText,
+  selectedText: trigger.textContent?.trim(),
+};
+```
+
+Verify with page state after running the script: selected label, sorted result order, result count, URL/query state, or another user-visible condition.

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/debugging-and-evidence.md

@@ -1,129 +1,129 @@
-# Debugging and Evidence
-
-Debugging is for evidence. Fallback is for completing operations.
-
-Use this file when you need to prove browser state, explain a failure, or collect artifacts for review. Do not use `execute-js` as the first debug tool.
-
-Use a unique workflow/debug token per task, such as `debug-checkout` or `debug-research`. Do not share one global `debug` token across independent agents.
-
-## Screenshot
-
-Use screenshots when visual layout, canvas, dialogs, or visual regressions matter.
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot screenshot --tab-id <TAB_ID> -o /tmp/omni-shot.png
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot screenshot --annotate --tab-id <TAB_ID> -o /tmp/omni-annotated.png
-```
-
-Prefer text extraction when text is enough. Screenshot is evidence, not extraction.
-
-## Console
-
-Use console logs for runtime JavaScript errors, frontend warnings, or app-level diagnostics.
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console errors --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console logs --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console clear --tab-id <TAB_ID>
-```
-
-Collect console diagnostics before and after the action when debugging regressions. `console errors` currently uses the console log collection path; verify level filtering in output before treating it as error-only evidence.
-
-## Network
-
-Use network logs for failed requests, redirects, blocked assets, API errors, or loading stalls.
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot network summary --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot network logs --tab-id <TAB_ID>
-```
-
-Pair network evidence with page verification:
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get text "#main" --tab-id <TAB_ID>
-```
-
-## Network Capture
-
-Use this when the user asks to capture API requests, checkout requests, submit requests, redirect chains, or CDP/network evidence around a specific browser action.
-
-Required order:
-
-1. Discover the tab id with `omnibot tabs`.
-2. Verify network command syntax with `omnibot network --help` and `omnibot network start --help` if this is the first network operation in the session.
-3. Clear old logs.
-4. Start capture.
-5. Perform exactly one browser action.
-6. Verify the page state changed.
-7. Stop capture.
-8. Read logs and summary.
-9. Report host, path, method, status, initiator, and non-sensitive payload shape. Do not reveal cookies, auth headers, full addresses, full phone numbers, payment data, or final order submission tokens.
-
-Example:
-
-```bash
-OMNIBOT_SESSION_TOKEN=checkout omnibot tabs
-OMNIBOT_SESSION_TOKEN=checkout omnibot network clear --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot network start --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot click --tab-id <TAB_ID> @e12
-OMNIBOT_SESSION_TOKEN=checkout omnibot wait --url "/checkout" --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot network stop --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot network summary --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot network logs --tab-id <TAB_ID>
-```
-
-If `network logs` returns an extension capability error, report that Omnibot needs the newer browser extension and fall back to `cdp Page.getNavigationHistory` plus `get url` for navigation evidence.
-
-## Trace
-
-Use trace for a reproducible artifact around a failing workflow.
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot trace start
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot click --tab-id <TAB_ID> @e4
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot trace stop -o trace.zip
-```
-
-Trace is evidence. It does not replace operation verification.
-
-## Record and Replay
-
-Use record/replay when a flow must be captured or reproduced.
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot record start
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot click --tab-id <TAB_ID> @e4
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot record stop -o flow.json
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot replay flow.json
-```
-
-After replay, verify final state:
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get url --tab-id <TAB_ID>
-```
-
-## CDP Inspection
-
-Use CDP for low-level inspection when normal evidence is insufficient.
-
-```bash
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot cdp Runtime.evaluate '{"expression":"document.title"}' --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug-checkout omnibot cdp DOM.getDocument '{"depth":1}' --tab-id <TAB_ID>
-```
-
-CDP inspection is not a first-choice operation path. If CDP changes state, it becomes Tier 7 fallback and must follow `fallback-operations.md#raw-cdp-fallback`.
-
-## Evidence Checklist
-
-Before reporting a browser issue, collect the smallest evidence set that explains it:
-
-- Runtime: `doctor`, `tabs`, `visibility status`.
-- Page state: `get`, `is`, `snapshot`, or `wait`.
-- Visual proof: `screenshot --annotate` only if visual state matters.
-- Browser diagnostics: `console errors` and `network summary`.
-- Reproduction artifact: `trace` or `record` when the flow is unstable.
+# Debugging and Evidence
+
+Debugging is for evidence. Fallback is for completing operations.
+
+Use this file when you need to prove browser state, explain a failure, or collect artifacts for review. Do not use `execute-js` as the first debug tool.
+
+Use a unique workflow/debug token per task, such as `debug-checkout` or `debug-research`. Do not share one global `debug` token across independent agents.
+
+## Screenshot
+
+Use screenshots when visual layout, canvas, dialogs, or visual regressions matter.
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot screenshot --tab-id <TAB_ID> -o /tmp/omni-shot.png
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot screenshot --annotate --tab-id <TAB_ID> -o /tmp/omni-annotated.png
+```
+
+Prefer text extraction when text is enough. Screenshot is evidence, not extraction.
+
+## Console
+
+Use console logs for runtime JavaScript errors, frontend warnings, or app-level diagnostics.
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console errors --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console logs --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console clear --tab-id <TAB_ID>
+```
+
+Collect console diagnostics before and after the action when debugging regressions. `console errors` currently uses the console log collection path; verify level filtering in output before treating it as error-only evidence.
+
+## Network
+
+Use network logs for failed requests, redirects, blocked assets, API errors, or loading stalls.
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot network summary --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot network logs --tab-id <TAB_ID>
+```
+
+Pair network evidence with page verification:
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get text "#main" --tab-id <TAB_ID>
+```
+
+## Network Capture
+
+Use this when the user asks to capture API requests, checkout requests, submit requests, redirect chains, or CDP/network evidence around a specific browser action.
+
+Required order:
+
+1. Discover the tab id with `omnibot tabs`.
+2. Verify network command syntax with `omnibot network --help` and `omnibot network start --help` if this is the first network operation in the session.
+3. Clear old logs.
+4. Start capture.
+5. Perform exactly one browser action.
+6. Verify the page state changed.
+7. Stop capture.
+8. Read logs and summary.
+9. Report host, path, method, status, initiator, and non-sensitive payload shape. Do not reveal cookies, auth headers, full addresses, full phone numbers, payment data, or final order submission tokens.
+
+Example:
+
+```bash
+OMNIBOT_SESSION_TOKEN=checkout omnibot tabs
+OMNIBOT_SESSION_TOKEN=checkout omnibot network clear --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot network start --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot snapshot -i --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot click --tab-id <TAB_ID> @e12
+OMNIBOT_SESSION_TOKEN=checkout omnibot wait --url "/checkout" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot network stop --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot network summary --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot network logs --tab-id <TAB_ID>
+```
+
+If `network logs` returns an extension capability error, report that Omnibot needs the newer browser extension and fall back to `cdp Page.getNavigationHistory` plus `get url` for navigation evidence.
+
+## Trace
+
+Use trace for a reproducible artifact around a failing workflow.
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot trace start
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot click --tab-id <TAB_ID> @e4
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot snapshot -i --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot trace stop -o trace.zip
+```
+
+Trace is evidence. It does not replace operation verification.
+
+## Record and Replay
+
+Use record/replay when a flow must be captured or reproduced.
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot record start
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot click --tab-id <TAB_ID> @e4
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot snapshot -i --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot record stop -o flow.json
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot replay flow.json
+```
+
+After replay, verify final state:
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get url --tab-id <TAB_ID>
+```
+
+## CDP Inspection
+
+Use CDP for low-level inspection when normal evidence is insufficient.
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot cdp Runtime.evaluate '{"expression":"document.title"}' --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot cdp DOM.getDocument '{"depth":1}' --tab-id <TAB_ID>
+```
+
+CDP inspection is not a first-choice operation path. If CDP changes state, it becomes Tier 7 fallback and must follow `fallback-operations.md#raw-cdp-fallback`.
+
+## Evidence Checklist
+
+Before reporting a browser issue, collect the smallest evidence set that explains it:
+
+- Runtime: `doctor`, `tabs`, `visibility status`.
+- Page state: `get`, `is`, `snapshot`, or `wait`.
+- Visual proof: `screenshot --annotate` only if visual state matters.
+- Browser diagnostics: `console errors` and `network summary`.
+- Reproduction artifact: `trace` or `record` when the flow is unstable.