@omniaibot/win-x64 1.1.6 → 1.4.0

package/bin/omnibot-windows-x64/VERSION

@@ -1 +1 @@
-1.1.6
+v1.4.0

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/SKILL.md

@@ -5,7 +5,7 @@ compatibility: Requires omnibot v2 CLI daemon and the omnibot Chromium extension
 allowed-tools: Bash
 metadata:
   author: omnibot
-  version: "2.1.0"
+  version: "2.2.0"
 ---
 
 # Omnibot
@@ -19,7 +19,7 @@ This skill is an execution specification for agents. It is not a human command m
 ## When to Use
 
 - Use Omnibot when browser runtime state matters: login, cookies, storage, client-side rendering, extensions, or visible user tabs.
-- Use Omnibot when an agent must read rendered pages, click controls, fill forms, upload files, navigate, extract content, or collect evidence.
+- Use Omnibot when an agent must read rendered pages, click controls, fill forms, navigate, extract content, or collect evidence.
 - Do not use Omnibot when static files or plain HTTP content already answer the task.
 
 ## Core Rules
@@ -35,16 +35,16 @@ This skill is an execution specification for agents. It is not a human command m
 - Parse JSON output from commands that return JSON.
 - Do not claim success without verification evidence.
 
-## Session + Tab Double Lock
+## Workflow Context + Tab Target
 
 Every page-state workflow must use both controls:
 
 - `OMNIBOT_SESSION_TOKEN=<workflow-name>` for workflow isolation.
 - `--tab-id <TAB_ID>` for page targeting.
 
-They are not substitutes. Session controls which workflow owns state. Tab ID controls which page receives the command.
+OMNIBOT_SESSION_TOKEN is a workflow/context token, not a browser session and not a tab target. It isolates agent state such as refs, trace, recording, aliases, and temporary resources. Tab ID controls which page receives the command.
 
-Do not rely on default tab, active tab, current tab, or prior targeting state. Every page command requires explicit `--tab-id`.
+Do not rely on default tab, active tab, current tab, or prior targeting state. Every page-state command requires explicit `--tab-id` except when the command is only discovering or creating a tab.
 
 Use the same token inside one workflow. Use different tokens for independent workflows.
 
@@ -56,7 +56,7 @@ OMNIBOT_SESSION_TOKEN=research omnibot click --tab-id <TAB_ID> @e4
 OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
 ```
 
-`@eN` refs are tab-scoped. never reuse `@eN` refs across tabs.
+`@eN` refs are tab-scoped. Refs rule: never reuse `@eN` refs across tabs.
 
 The agent dispatch pattern is token + tab-id:
 
@@ -75,6 +75,14 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot dom dblclick n1 --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot clipboard read --tab-id <TAB_ID>
 ```
 
+Targeting categories:
+
+| Command category | Rule |
+| --- | --- |
+| Page-state commands: `snapshot`, `click`, `fill`, `type`, `get`, `is`, `wait`, `screenshot`, `console`, `network`, `execute-js`, `dom`, `mouse`, `clipboard`, `viewport`, `assets`, `goto`, same-tab `navigate` | Require `--tab-id <TAB_ID>`. |
+| Discovery or tab creation: `tabs`, `tab list`, `tab new <URL>`, `open <URL>`, `navigate <URL>` | Return or discover the tab id; save it for later page-state commands. |
+| Read URL exception: `read <URL>` | Opens a temporary read tab and does not need `--tab-id`; reading an existing tab still requires `read --tab-id <TAB_ID>`. |
+
 ## Observe -> Act -> Verify
 
 All page operations must follow this loop:
@@ -104,7 +112,7 @@ If verification fails, do not repeat blindly. Re-observe, choose the next fallba
 
 ## Pattern > Command
 
-Start from the task, not the command name. Use operation patterns for read, click, fill, select/check, navigation, wait, extraction, upload, and batch.
+Start from the task, not the command name. Use operation patterns for read, click, fill, select/check, navigation, wait, extraction, and batch.
 
 Use fallback tiers only after standard patterns fail. Collect evidence separately from fallback execution. The command reference is only a lookup table; it must not decide behavior.
 
@@ -133,7 +141,6 @@ Do not use `read` as the first step for click/fill workflows unless the user exp
 | Navigation | `references/operation-patterns.md#navigation` |
 | Waiting | `references/operation-patterns.md#wait` |
 | Extraction | `references/operation-patterns.md#extraction` |
-| Upload | `references/operation-patterns.md#upload` |
 | Batch | `references/operation-patterns.md#batch` |
 | Fallback | `references/fallback-operations.md` |
 | Tabs and sessions | `references/session-and-tabs.md` |
@@ -182,7 +189,7 @@ Use screenshots, annotated screenshots, console logs, network logs, trace, recor
 - Missing `OMNIBOT_SESSION_TOKEN` or missing `--tab-id` on page-state commands.
 - Acting without verify or claiming success without evidence.
 - Using `execute-js` first, raw CSS before semantic find, `@eN` across tabs, implicit tab targeting, or shell sleep instead of `omnibot wait`.
-- Using removed commands: `switch-tab`, `focus-tab`, `tab switch`. These are no longer available.
+- Using removed commands: `switch-tab`, `focus-tab`, `tab switch`, `tab focus`. These are no longer available.
 - Using `tabs[0]` or the first tab as a target. The first tab is often a user tab or transport tab.
 - Closing user tabs discovered during cleanup. Only close tabs created by the current workflow.
 

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/command-reference.md

@@ -2,6 +2,8 @@
 
 This is a lookup table, not a behavior guide. Choose behavior from `operation-patterns.md`, use `session-and-tabs.md` for targeting, and use `fallback-operations.md` before dropping to lower tiers.
 
+Unless marked as discovery, runtime, or tab creation, page-state examples assume `OMNIBOT_SESSION_TOKEN=<workflow>` and `--tab-id <TAB_ID>`.
+
 ## Runtime & Status
 
 ### doctor
@@ -270,14 +272,28 @@ Fallback relation: Mouse drag is Tier 5 if element drag fails.
 
 ### upload
 
-Purpose: Upload a local file through a file input.
+Purpose: Reserved command for local file upload. Native upload is currently unavailable in the extension transport.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=form omnibot upload "input[type=file]" /path/to/file.png --tab-id <TAB_ID>
+# Do not use in agent workflows until file chooser support is implemented.
 ```
 
 Preferred pattern: See `operation-patterns.md#upload`.
-Fallback relation: Use JavaScript only if native upload cannot reach the input.
+Fallback relation: Do not treat JavaScript as a normal upload fallback.
+
+### keyboard / keydown / keyup
+
+Purpose: Send keyboard text or key state to the target tab when element-specific `type` or `press` is insufficient.
+
+```bash
+OMNIBOT_SESSION_TOKEN=form omnibot keyboard type "hello" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=form omnibot keyboard inserttext "hello" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=form omnibot keydown Shift --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=form omnibot keyup Shift --tab-id <TAB_ID>
+```
+
+Preferred pattern: Prefer `fill`, `type`, and `press` first.
+Fallback relation: Keyboard commands are a focused fallback before mouse or JavaScript.
 
 ## Semantic Find
 
@@ -347,8 +363,8 @@ Purpose: Send raw Chrome DevTools Protocol commands.
 Usage tier: Tier 7 fallback and inspection only.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot cdp Runtime.evaluate '{"expression":"document.title"}' --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot cdp DOM.getDocument '{"depth":1}' --tab-id <TAB_ID>
+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>
 ```
 
 Preferred pattern: See `fallback-operations.md#raw-cdp-fallback` and `debugging-and-evidence.md#cdp-inspection`.
@@ -358,13 +374,13 @@ Fallback relation: Last resort.
 
 ### navigate / open / goto
 
-Purpose: Navigate or open pages. These commands create or use CLI target state; record the resulting tab id and use `--tab-id` afterward.
+Purpose: Navigate or open pages. New-tab forms return a tab id. Same-tab navigation requires an explicit target tab id. There is no CLI current-tab state.
 
 ```bash
 OMNIBOT_SESSION_TOKEN=research omnibot navigate https://example.com
-OMNIBOT_SESSION_TOKEN=research omnibot navigate --same-tab https://example.com
+OMNIBOT_SESSION_TOKEN=research omnibot navigate https://example.com --same-tab --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot open https://example.com
-OMNIBOT_SESSION_TOKEN=research omnibot goto https://example.com
+OMNIBOT_SESSION_TOKEN=research omnibot goto https://example.com --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#navigation` and `session-and-tabs.md#tab-explicit`.
@@ -414,7 +430,6 @@ OMNIBOT_SESSION_TOKEN=research omnibot frame main
 Purpose: Wait for time, selector, text, URL, load state, or JavaScript condition.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=checkout omnibot wait 500 --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot wait "#ready" --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot wait "#spinner" --state hidden --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot wait --text "Welcome" --tab-id <TAB_ID>
@@ -422,17 +437,18 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot wait --url "/dashboard" --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot wait --load domcontentloaded --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot wait --load networkidle --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=checkout omnibot wait --fn "window.appReady === true" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot wait 500 --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#wait`.
-Fallback relation: Prefer over shell sleep.
+Fallback relation: Prefer condition waits over shell sleep. Fixed-time waits like `wait 500` are diagnostic or last resort only.
 
 ### batch
 
-Purpose: Send short command arrays as JSON or from a file.
+Purpose: Send short extension/CDP command arrays as JSON or from a file. Batch is not a wrapper for normal CLI commands such as `snapshot` or `click`.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"cdp","method":"Runtime.evaluate","params":{"expression":"document.title","returnByValue":true}}]' --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot batch --file /tmp/omnibot-batch.json --tab-id <TAB_ID>
 ```
 
@@ -446,8 +462,8 @@ Fallback relation: Not a substitute for verification.
 Purpose: Capture visual evidence from a browser tab.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot screenshot --tab-id <TAB_ID> -o /tmp/omni-shot.png
-OMNIBOT_SESSION_TOKEN=debug omnibot screenshot --annotate --tab-id <TAB_ID> -o /tmp/omni-annotated.png
+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
 ```
 
 Preferred pattern: See `debugging-and-evidence.md#screenshot`.
@@ -458,21 +474,21 @@ Fallback relation: Evidence collection, not operation fallback.
 Purpose: Read or clear browser console evidence.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot console logs --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot console errors --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot console clear --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console logs --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console errors --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot console clear --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `debugging-and-evidence.md#console`.
-Fallback relation: Evidence collection, not operation fallback.
+Fallback relation: Evidence collection, not operation fallback. `console errors` currently uses the console log collection path; verify level filtering in output before treating it as error-only evidence.
 
 ### network
 
 Purpose: Read browser network evidence.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot network logs --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot network summary --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot network logs --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot network summary --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `debugging-and-evidence.md#network`.
@@ -520,18 +536,17 @@ Fallback relation: Use after page content indicates assets are needed.
 
 ### visibility
 
-Purpose: Inspect, set, or launch automation browser visibility mode.
+Purpose: Inspect or set automation browser visibility mode. `visibility launch` currently reports planned configuration only; it does not launch a browser.
 
 ```bash
 omnibot visibility status
 omnibot visibility set background
 omnibot visibility set visible
-omnibot visibility set headless --user-data-dir /tmp/omnibot-headless
 omnibot visibility launch headless --user-data-dir /tmp/omnibot-headless
 ```
 
 Preferred pattern: See `session-and-tabs.md#visibility`.
-Fallback relation: Headless does not inherit existing user login state.
+Fallback relation: Headless does not inherit existing user login state. Treat `visibility launch` status `planned` as not launched.
 
 ### browser
 
@@ -549,7 +564,7 @@ Fallback relation: Use in multi-browser or multi-runtime scenarios.
 
 ### session
 
-Purpose: Name or list sessions.
+Purpose: Name or list Omnibot workflow context state for the current `OMNIBOT_SESSION_TOKEN`. This does not switch tabs, preserve login, or replace `--tab-id`.
 
 ```bash
 OMNIBOT_SESSION_TOKEN=checkout omnibot session name "checkout"
@@ -566,11 +581,11 @@ Fallback relation: Not a fallback command.
 Purpose: Capture, replay, or trace workflows for evidence.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot record start
-OMNIBOT_SESSION_TOKEN=debug omnibot record stop -o flow.json
-OMNIBOT_SESSION_TOKEN=debug omnibot replay flow.json
-OMNIBOT_SESSION_TOKEN=debug omnibot trace start
-OMNIBOT_SESSION_TOKEN=debug omnibot trace stop -o trace.zip
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot record start
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot record stop -o flow.json
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot replay flow.json
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot trace start
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot trace stop -o trace.zip
 ```
 
 Preferred pattern: See `debugging-and-evidence.md#record-and-replay` and `debugging-and-evidence.md#trace`.

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

@@ -0,0 +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.

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

@@ -4,13 +4,15 @@ 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 omnibot screenshot --tab-id <TAB_ID> -o /tmp/omni-shot.png
-OMNIBOT_SESSION_TOKEN=debug omnibot screenshot --annotate --tab-id <TAB_ID> -o /tmp/omni-annotated.png
+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.
@@ -20,26 +22,26 @@ Prefer text extraction when text is enough. Screenshot is evidence, not extracti
 Use console logs for runtime JavaScript errors, frontend warnings, or app-level diagnostics.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot console errors --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot console logs --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot console clear --tab-id <TAB_ID>
+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 errors before and after the action when debugging regressions.
+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 omnibot network summary --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot network logs --tab-id <TAB_ID>
+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 omnibot get text "#main" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get text "#main" --tab-id <TAB_ID>
 ```
 
 ## Trace
@@ -47,10 +49,10 @@ OMNIBOT_SESSION_TOKEN=debug omnibot get text "#main" --tab-id <TAB_ID>
 Use trace for a reproducible artifact around a failing workflow.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot trace start
-OMNIBOT_SESSION_TOKEN=debug omnibot click --tab-id <TAB_ID> @e4
-OMNIBOT_SESSION_TOKEN=debug omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot trace stop -o trace.zip
+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.
@@ -60,17 +62,17 @@ Trace is evidence. It does not replace operation verification.
 Use record/replay when a flow must be captured or reproduced.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot record start
-OMNIBOT_SESSION_TOKEN=debug omnibot click --tab-id <TAB_ID> @e4
-OMNIBOT_SESSION_TOKEN=debug omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot record stop -o flow.json
-OMNIBOT_SESSION_TOKEN=debug omnibot replay flow.json
+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 omnibot get url --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get url --tab-id <TAB_ID>
 ```
 
 ## CDP Inspection
@@ -78,8 +80,8 @@ OMNIBOT_SESSION_TOKEN=debug omnibot get url --tab-id <TAB_ID>
 Use CDP for low-level inspection when normal evidence is insufficient.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot cdp Runtime.evaluate '{"expression":"document.title"}' --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot cdp DOM.getDocument '{"depth":1}' --tab-id <TAB_ID>
+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`.

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/fallback-operations.md

@@ -134,60 +134,15 @@ OMNIBOT_SESSION_TOKEN=repair omnibot wait --url "/dashboard" --tab-id <TAB_ID>
 
 Use this only after the trigger is known and higher tiers failed: semantic `find` clicked the trigger or found the text, `snapshot -i` could not expose option refs, selector/DOM/mouse could not complete the two-step interaction, and verification showed the selection did not change.
 
-Example for a visible trigger like `按留言时间排序` and a target option text:
+Use a short `execute-js --file` script and verify the user-visible result, not just `{ ok: true }`: selected label, sorted result order, result count, URL/query state, or another page-specific condition.
+
+Detailed recipe: `css-only-dropdown-js.md`.
 
 ```bash
 OMNIBOT_SESSION_TOKEN=repair omnibot execute-js --file /tmp/omnibot-css-dropdown.js --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=repair omnibot snapshot -i --tab-id <TAB_ID>
 ```
 
-`/tmp/omnibot-css-dropdown.js`:
-
-```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 the user-visible result, not just `{ ok: true }`: selected label, sorted result order, result count, URL/query state, or another page-specific condition.
-
 Prefer `--file` for longer scripts:
 
 ```bash
@@ -202,15 +157,15 @@ OMNIBOT_SESSION_TOKEN=repair omnibot snapshot -i --tab-id <TAB_ID>
 Raw CDP is the last resort. Use it only when standard commands and JavaScript fallback cannot complete or inspect the task.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot cdp Runtime.evaluate '{"expression":"document.title"}' --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot cdp DOM.getDocument '{"depth":1}' --tab-id <TAB_ID>
+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>
 ```
 
 After CDP fallback, verify using normal Omnibot reads whenever possible:
 
 ```bash
-OMNIBOT_SESSION_TOKEN=debug omnibot get title --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=debug omnibot snapshot -i --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot get title --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=debug-checkout omnibot snapshot -i --tab-id <TAB_ID>
 ```
 
 CDP can bypass application-level event semantics. Treat it as expert-only infrastructure access.

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/operation-patterns.md

@@ -214,9 +214,9 @@ Other navigation commands:
 
 ```bash
 OMNIBOT_SESSION_TOKEN=research omnibot navigate https://example.com
-OMNIBOT_SESSION_TOKEN=research omnibot navigate --same-tab https://example.com
+OMNIBOT_SESSION_TOKEN=research omnibot navigate https://example.com --same-tab --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot open https://example.com
-OMNIBOT_SESSION_TOKEN=research omnibot goto https://example.com
+OMNIBOT_SESSION_TOKEN=research omnibot goto https://example.com --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot pushstate /dashboard --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot close <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot tab list
@@ -321,25 +321,24 @@ If content exists only in runtime objects, use `fallback-operations.md#javascrip
 
 ### When to use
 
-Use Upload when a browser form needs a local file attached through a file input.
+Native upload is currently unavailable in the extension transport. Do not use `omnibot upload` as an agent workflow step until file chooser support is implemented.
 
 ### Preferred sequence
 
-1. Observe the file input or upload control.
-2. Use `upload` against the input selector.
-3. Verify that the uploaded file appeared or form state changed.
+1. Observe the upload UI and confirm the task requires a local file.
+2. Report that native upload is currently unavailable.
+3. If the user still wants a workaround, ask for approval before using page-specific JavaScript or manual browser interaction.
 
 ### Example
 
 ```bash
 OMNIBOT_SESSION_TOKEN=form omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=form omnibot upload "input[type=file]" /path/to/file.png --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=form omnibot wait --text "file.png" --tab-id <TAB_ID>
+# upload is currently unavailable; do not run omnibot upload here.
 ```
 
 ### Verification
 
-Use visible filename, count, enabled submit state, or application-specific confirmation:
+If upload support is implemented later, verify with visible filename, count, enabled submit state, or application-specific confirmation:
 
 ```bash
 OMNIBOT_SESSION_TOKEN=form omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
@@ -347,13 +346,13 @@ OMNIBOT_SESSION_TOKEN=form omnibot is enabled "button[type=submit]" --tab-id <TA
 
 ### Fallback entry point
 
-If upload input is hidden behind custom UI, click the semantic upload control first. Use JavaScript only after standard upload cannot reach the input.
+Do not treat JavaScript as a normal upload fallback. File inputs and browser file chooser behavior are security-sensitive and page-specific.
 
 ## Batch
 
 ### When to use
 
-Use Batch for short, known-safe command chains where the target tab and verification are already explicit.
+Use Batch for short, known-safe extension/CDP command chains where the target tab and verification are already explicit. Batch is not a wrapper for normal CLI commands such as `snapshot` or `click`.
 
 ### Preferred sequence
 
@@ -365,8 +364,8 @@ Use Batch for short, known-safe command chains where the target tab and verifica
 ### Example
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"cdp","method":"Runtime.evaluate","params":{"expression":"document.title","returnByValue":true}}]' --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot get title --tab-id <TAB_ID>
 ```
 
 File example: