@omniaibot/win-x64 1.6.4 → 1.6.5

package/bin/omnibot-windows-x64/VERSION

@@ -1 +1 @@
-1.6.3
+1.6.5 

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

@@ -140,6 +140,18 @@ Do not use `read` as the first step for click/fill workflows unless the user exp
 
 Use `select @combobox "value"` for native selects or simple controls. Use `click @option` when `snapshot -i` exposes auto-probed combobox option refs. Do not manually reopen every dropdown just to discover options unless `snapshot -i` did not expose option refs.
 
+## Rich Text Article Editors
+
+ContentEditable rich text editors (ProseMirror, Quill, Draft.js, Slate, ByteDance/Toutiao article body, etc.) are often missing from the AX tree. `snapshot -i` appends them under `# DOM Rich Text Editors` as `@eN [richtext] "..." [contenteditable=true]` refs.
+
+- Detect the body editor: `snapshot -i` → look for `@eN [richtext]` under `# DOM Rich Text Editors`. Do not fill the article body through a `[textbox]` title ref.
+- Replace the whole body: `fill @richtext "paragraph 1\n\nparagraph 2"`. Empty lines split paragraphs; the previous content is cleared and `input`/`change` events are dispatched.
+- Append to the body: `type @richtext " additional text"`.
+- Focus before keyboard input: click `@richtext` first, then `press`/`keyboard`.
+- Raw selector fallback: `omnibot fill '[contenteditable="true"]' "..."` also routes through the rich text path when the selector looks like a rich editor.
+
+Do not use `execute-js` first for rich text writes; `fill`/`type` on the `[richtext]` ref is the supported path.
+
 ## Quick Routing
 
 | Need | Read |

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

@@ -28,6 +28,10 @@
 | Revealing sensitive network data | Cookies, auth headers, full addresses, phone numbers, and payment data must not be pasted into reports. | Report host, path, method, status, and non-sensitive payload shape only. |
 | Using stale `@eN` refs after a failed click | Refs may have expired or the page may have changed. | Re-observe with `snapshot -i` or use a higher-evidence fallback. |
 | `Network.enable` without log retrieval | Raw `cdp` calls are one-shot and do not persist events for later reading. | Use `network clear -> network start -> one action -> network stop -> network logs/summary`. |
+| Writing the article body into the title field | Rich text article body editors are often missing from the AX tree; filling the only visible `[textbox]` (title) overwrites the wrong control. | Run `snapshot -i`, find the body under `# DOM Rich Text Editors` as `@eN [richtext]`, then `fill @richtext "..."`. |
+| `execute-js` for rich text body before `fill @richtext` | ContentEditable writes need event dispatch and framework integration; ad-hoc `innerHTML` bypasses Omnibot's supported path. | Use `fill @richtext "p1\n\np2"` or `type @richtext " text"` first. |
+| Counting `<img>` nodes to detect duplicate images in a rich editor | ProseMirror/Toutiao image cards keep a hidden `<templ>` template and a visible `<mask>` copy of the same `<img>`, so `.ProseMirror img` returns 2 for one logical image and falsely reports duplication. | Count image card containers (`.ProseMirror [__syl_tag=true]` or `.ProseMirror .pgc-image`), one per inserted image. |
+| Inserting an image via `click @richtext` + `press End` | The caret stays on the first line; the image lands at the editor root instead of the target paragraph. | Use `find text "<anchor phrase>" --action click` to collapse the selection at the end of the matched phrase, then open the image tool and upload. |
 
 Do not manually reopen a dropdown just to discover options if `snapshot -i` already lists them.
 
@@ -45,5 +49,9 @@ Do not manually reopen a dropdown just to discover options if `snapshot -i` alre
 - "I remember the command syntax from before."
 - "`Network.enable` should be enough to capture requests."
 - "It is just a checkout preview, clicking pay should be fine."
+- "The article body is not in `snapshot -i`, so I will fill the title textbox."
+- "I will just set `innerHTML` on the contenteditable with `execute-js`."
+- "`.ProseMirror img` returned 2, so the image was inserted twice."
+- "I clicked the editor and pressed End, so the caret must be after the last paragraph."
 
 All of these mean: stop, re-enter the standard pattern, and make state explicit.

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

@@ -174,6 +174,8 @@ Fallback relation: Tier 2 with refs, Tier 3 with selector.
 
 Combobox option refs: if `snapshot -i` shows `@eN [option] "OpenAI Chat"`, prefer `click @eN` over JavaScript fallback. Omnibot will reopen the owning combobox when needed.
 
+Rich text editor refs: if `snapshot -i` shows `@eN [richtext] "..." [contenteditable=true]` under `# DOM Rich Text Editors`, treat it as the article body editor. Use `fill @richtext` to replace the whole body (supports `\n\n` for paragraphs) and `type @richtext` to append. Do not fall back to `execute-js` first.
+
 ### dblclick
 
 Purpose: Double-click an element by `@eN` ref or selector.
@@ -197,6 +199,14 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot fill "input[name=email]" "a@b.com" --tab-
 Preferred pattern: See `operation-patterns.md#fill`.
 Fallback relation: Tier 2 with refs, Tier 3 with selector.
 
+Rich text body editors (ProseMirror/Quill/Draft.js/Slate/Toutiao article body): if the target is an `@eN [richtext]` ref, `fill` writes through a dedicated contenteditable path that clears the previous body and dispatches `input`/`change` events. Split paragraphs with an empty line:
+
+```bash
+OMNIBOT_SESSION_TOKEN=editor omnibot fill --tab-id <TAB_ID> @eN "First paragraph.\n\nSecond paragraph."
+```
+
+Raw selector fallback is supported for selectors that look like a rich editor (e.g. `[contenteditable="true"]`, `.ProseMirror`, `.ql-editor`).
+
 ### type
 
 Purpose: Type text into an element.
@@ -208,6 +218,8 @@ OMNIBOT_SESSION_TOKEN=search omnibot type --tab-id <TAB_ID> @e3 "omnibot"
 Preferred pattern: See `operation-patterns.md#fill`.
 Fallback relation: Use after fill is not appropriate or focus is needed.
 
+For `@eN [richtext]` article body editors, `type` appends at the cursor position. Click the `@richtext` ref first to focus the editor.
+
 ### press
 
 Purpose: Press a key in the target tab.
@@ -290,14 +302,14 @@ Fallback relation: Mouse drag is Tier 5 if element drag fails.
 
 ### upload
 
-Purpose: Reserved command for local file upload. Native upload is currently unavailable in the extension transport.
+Purpose: Attach a local file to an `<input type="file">` element via CDP (`DOM.setFileInputFiles`), with nodeId and JS `DataTransfer` fallbacks.
 
 ```bash
-# Do not use in agent workflows until file chooser support is implemented.
+OMNIBOT_SESSION_TOKEN=form omnibot upload "input[type=file]" /path/to/file.png --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#upload`.
-Fallback relation: Do not treat JavaScript as a normal upload fallback.
+Fallback relation: The CLI falls back from CDP objectId → CDP nodeId → JS DataTransfer. Do not stack additional JavaScript fallbacks.
 
 ### keyboard / keydown / keyup
 
@@ -326,6 +338,8 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot find testid submit-button --action click
 OMNIBOT_SESSION_TOKEN=checkout omnibot find nth ".card" 2 --action click --tab-id <TAB_ID>
 ```
 
+Text-node precision: `find text` walks the DOM text nodes and marks the nearest visible container of the matching text, not the first ancestor whose `textContent` happens to include the needle. The matched offset/length is stored on the element, so `--action click` positions the mouse at the end of the matched text. Inside a `contenteditable` body (ProseMirror/Quill/etc.), the selection is collapsed right after the matched text and the editor is focused, so a follow-up image insertion lands at the intended paragraph instead of the editor root.
+
 Preferred pattern: See `operation-patterns.md#click` and `operation-patterns.md#fill`.
 Fallback relation: Tier 1. Explain failure before using refs, selectors, DOM, mouse, JavaScript, or CDP.
 

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

@@ -109,6 +109,8 @@ Use `execute-js` only when:
 - A CSS-only dropdown or hover menu requires an atomic open-then-select sequence, and `snapshot -i` confirms the option nodes are absent from the accessibility tree.
 - Runtime state cannot be read through `read`, `snapshot`, `get`, or `is`.
 
+Rich text article body editors (`@eN [richtext]`, `.ProseMirror`, `.ql-editor`, `[contenteditable="true"]`) have native `fill`/`type` support. Do not fall back to JavaScript for richtext writes; use `fill @richtext "..."` first.
+
 Read-only JavaScript fallback:
 
 ```bash

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

@@ -99,7 +99,7 @@ When `snapshot -i` shows only `StaticText` for a visible control label, do not a
 
 ### When to use
 
-Use Fill for text inputs, textareas, search boxes, login fields, and form fields where the final value must be controlled.
+Use Fill for text inputs, textareas, search boxes, login fields, form fields where the final value must be controlled, and rich text article body editors (contenteditable ProseMirror/Quill/Draft.js/Slate/Toutiao article body).
 
 ### Preferred sequence
 
@@ -124,6 +124,21 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot fill --tab-id <TAB_ID> @e2 "a@b.com"
 OMNIBOT_SESSION_TOKEN=checkout omnibot get value "input[name=email]" --tab-id <TAB_ID>
 ```
 
+### Rich text article body
+
+For article body editors exposed as `@eN [richtext] "..." [contenteditable=true]` under `# DOM Rich Text Editors`:
+
+```bash
+OMNIBOT_SESSION_TOKEN=editor omnibot snapshot -i --tab-id <TAB_ID>
+# Body appears under "# DOM Rich Text Editors": @eN [richtext] "..."
+OMNIBOT_SESSION_TOKEN=editor omnibot fill --tab-id <TAB_ID> @eN "First paragraph.\n\nSecond paragraph."
+OMNIBOT_SESSION_TOKEN=editor omnibot snapshot -i --tab-id <TAB_ID>  # verify body content replaced
+```
+
+- `\n\n` splits paragraphs; previous content is cleared.
+- `type @richtext " text"` appends at the cursor (click the ref first to focus).
+- Do NOT write the article body into a `[textbox]` title field. Title and richtext body are separate refs.
+
 ### Verification
 
 Use `get value`, visible validation text, enabled state, or submit readiness:
@@ -133,6 +148,24 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot get value "input[name=email]" --tab-id <T
 OMNIBOT_SESSION_TOKEN=checkout omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
 ```
 
+For richtext bodies, re-run `snapshot -i` and confirm the `@eN [richtext]` name matches the intended content.
+
+### Cursor positioning and inline image insertion
+
+For `contenteditable` article bodies (ProseMirror/Quill/Draft.js/Slate/Toutiao article body), `find text "<anchor phrase>" --action click` collapses the editor selection at the end of the matched phrase and focuses the editor. Use this to place the caret at a specific paragraph before inserting an image, typing, or pressing keys. Do not rely on a bare `click` of the editor followed by `press End`, because the caret would stay on the first line.
+
+Insert an image after a specific paragraph:
+
+```bash
+OMNIBOT_SESSION_TOKEN=editor omnibot find text "第二段锚点文字" --action click --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot click ".syl-toolbar-tool.image .syl-toolbar-button" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot wait --selector ".upload-image-panel input[type=file]" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot upload ".upload-image-panel input[type=file]" "/path/to/image.png" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot find role button --name "确定" --action click --tab-id <TAB_ID>
+```
+
+Verify the inserted image by counting visible image cards, not raw `<img>` nodes. Toutiao/ProseMirror image cards keep a hidden `<templ>` template and a visible `<mask>` copy of the same `<img>`, so `.ProseMirror img` returns 2 for one logical image. Count the image card container instead (e.g. `.ProseMirror [__syl_tag=true]` or `.ProseMirror .pgc-image`), which reports one per inserted image.
+
 ### Fallback entry point
 
 If fill does not update the application state, use `fallback-operations.md#javascript-fallback` only after selector/focus/type attempts fail. JavaScript must dispatch real `input` and `change` events.
@@ -333,32 +366,35 @@ If content exists only in runtime objects, use `fallback-operations.md#javascrip
 
 ### When to use
 
-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.
+Use `omnibot upload` to attach a local file to an `<input type="file">` element. The command speaks CDP (`DOM.setFileInputFiles`) through the extension debugger transport, with a JS `DataTransfer` fallback for pages that reject programmatic file assignment.
 
 ### Preferred sequence
 
 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.
+2. Locate the file input via `snapshot -i` or a CSS selector.
+3. Run `omnibot upload <selector> <local-file> --tab-id <TAB_ID>`.
+4. Verify the file was accepted (filename, count, enabled submit state, or application-specific confirmation).
 
 ### Example
 
 ```bash
 OMNIBOT_SESSION_TOKEN=form omnibot snapshot -i --tab-id <TAB_ID>
-# upload is currently unavailable; do not run omnibot upload here.
+OMNIBOT_SESSION_TOKEN=form omnibot upload "input[type=file]" /path/to/cover.png --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=form omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
 ```
 
 ### Verification
 
-If upload support is implemented later, verify with visible filename, count, enabled submit state, or application-specific confirmation:
+Confirm the input accepted the file:
 
 ```bash
+OMNIBOT_SESSION_TOKEN=form omnibot get "input[type=file]" attr value --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=form omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
 ```
 
 ### Fallback entry point
 
-Do not treat JavaScript as a normal upload fallback. File inputs and browser file chooser behavior are security-sensitive and page-specific.
+The CLI already falls back from CDP `DOM.setFileInputFiles` (by objectId, then nodeId) to a JS `DataTransfer` assignment. Do not add further JavaScript fallbacks on top; file inputs are security-sensitive and page-specific. If all three transports fail, report the failure to the user instead of scripting around it.
 
 ## Batch
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omniaibot/win-x64",
-  "version": "1.6.4",
+  "version": "1.6.5",
   "description": "omnibot executable for Windows x64",
   "os": [
     "win32"

package/bin/omnibot-win-x64/VERSION

@@ -1 +0,0 @@
-1.6.4

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

@@ -1,261 +0,0 @@
----
-name: omnibot
-description: Use when AI agents need to read, inspect, operate, navigate, debug, or verify browser state through the omnibot CLI and connected Chromium extension.
-compatibility: Requires omnibot v2 CLI daemon and the omnibot Chromium extension connected to 127.0.0.1:18765.
-allowed-tools: Bash
-metadata:
-  author: omnibot
-  version: "2.4.0"
----
-
-# Omnibot
-
-Omnibot is Browser Infrastructure for AI Agents.
-
-It connects Hermes, Claude Code, Codex, OpenCode, and other agent systems to a real Chromium browser through the local omnibot daemon and CLI.
-
-This skill is an execution specification for agents. It is not a human command manual.
-
-## 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, navigate, extract content, or collect evidence.
-- Do not use Omnibot when static files or plain HTTP content already answer the task.
-
-## Core Rules
-
-- Reliability > Convenience.
-- Explicit State > Implicit State.
-- Pattern > Command.
-- Observe -> Act -> Verify.
-- Fallback is allowed, but never first.
-- Do not use `execute-js` first.
-- Run `omnibot <command> --help` before using uncommon or newly introduced commands, especially `batch`, `network`, `cdp`, `record`, `trace`, and `skills`.
-- If a command from memory fails with parser errors, stop using that remembered syntax and re-check `omnibot --help` plus the subcommand help.
-- Prefer semantic locators and `snapshot -i` refs before selectors.
-- Raw `cdp` calls are one-shot. Do not assume `Network.enable` alone creates readable logs. For API/request evidence, use `network clear -> network start -> one action -> network stop -> network logs/summary`.
-- After a failed click by ref, re-observe or use a higher-evidence fallback. Do not keep using stale `@eN` refs from a previous snapshot.
-- For shopping, checkout, payment, banking, or irreversible workflows: Do not click final submit/pay/place-order controls unless the user explicitly confirms that final action in the current turn.
-- Prefer condition-based `wait` over shell sleep.
-- Parse JSON output from commands that return JSON.
-- Do not claim success without verification evidence.
-
-## 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.
-
-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-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.
-
-Standard form:
-
-```bash
-OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
-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. Refs rule: never reuse `@eN` refs across tabs.
-
-The agent dispatch pattern is token + tab-id:
-
-1. Set a stable `OMNIBOT_SESSION_TOKEN`.
-2. Discover or create the target tab.
-3. Save the returned tab id.
-4. Pass `--tab-id <TAB_ID>` on every command that touches page state.
-5. Run observe -> act -> verify on that same tab.
-
-Examples of tab-locked page-state commands:
-
-```bash
-OMNIBOT_SESSION_TOKEN=checkout omnibot get value "input[name=email]" --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot find placeholder "Search" --action type --action-value "omnibot" --tab-id <TAB_ID>
-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:
-
-1. Observe the current page state.
-2. Act once using the highest reliable pattern available.
-3. Verify the expected state change.
-
-Click example:
-
-```bash
-OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=research omnibot click --tab-id <TAB_ID> @e4
-OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
-```
-
-Read/verify example:
-
-```bash
-OMNIBOT_SESSION_TOKEN=checkout omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot find role button --name "Submit" --action click --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot wait --url "/dashboard" --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=checkout omnibot get url --tab-id <TAB_ID>
-```
-
-If verification fails, do not repeat blindly. Re-observe, choose the next fallback tier, and verify again.
-
-## Pattern > Command
-
-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.
-
-## Read vs Snapshot Routing
-
-Choose by intent before choosing by command name:
-
-| Intent | Prefer | Why |
-| --- | --- | --- |
-| Summarize or extract page content, article text, search results, feeds, or long/lazy pages | `read` | Returns clean text/Markdown for agent reasoning. |
-| Quickly observe current visible UI structure before deciding what to do next | `snapshot -i` | Returns actionable refs and page structure for routing. |
-| Find buttons, links, inputs, or refs for a later action | `find` or `snapshot -i` | Produces actionable targets; `read` does not. |
-| Verify one concrete condition | `get`, `is`, or `wait` | Narrow evidence is more reliable than dumping a page. |
-
-Do not use `read` as the first step for click/fill workflows unless the user explicitly asked for page content first.
-
-## Dropdowns And Custom Comboboxes
-
-`snapshot -i` may auto-probe visible custom comboboxes and append their options as refs. If the output lists `@eN [option] "..."`, click that option ref directly; Omnibot will reopen the owning combobox through `openerSelector` if the dropdown closed during snapshot.
-
-Use `select @combobox "value"` for native selects or simple controls. Use `click @option` when `snapshot -i` exposes auto-probed combobox option refs. Do not manually reopen every dropdown just to discover options unless `snapshot -i` did not expose option refs.
-
-## Rich Text Article Editors
-
-ContentEditable rich text editors (ProseMirror, Quill, Draft.js, Slate, ByteDance/Toutiao article body, etc.) are often missing from the AX tree. `snapshot -i` appends them under `# DOM Rich Text Editors` as `@eN [richtext] "..." [contenteditable=true]` refs.
-
-- Detect the body editor: `snapshot -i` → look for `@eN [richtext]` under `# DOM Rich Text Editors`. Do not fill the article body through a `[textbox]` title ref.
-- Replace the whole body: `fill @richtext "paragraph 1\n\nparagraph 2"`. Empty lines split paragraphs; the previous content is cleared and `input`/`change` events are dispatched.
-- Append to the body: `type @richtext " additional text"`.
-- Focus before keyboard input: click `@richtext` first, then `press`/`keyboard`.
-- Raw selector fallback: `omnibot fill '[contenteditable="true"]' "..."` also routes through the rich text path when the selector looks like a rich editor.
-
-Do not use `execute-js` first for rich text writes; `fill`/`type` on the `[richtext]` ref is the supported path.
-
-## Quick Routing
-
-| Need | Read |
-| --- | --- |
-| Runtime check | `references/runtime-and-status.md` |
-| Reading pages | `references/operation-patterns.md#read` |
-| Clicking | `references/operation-patterns.md#click` |
-| Filling forms | `references/operation-patterns.md#fill` |
-| Select / check | `references/operation-patterns.md#select--check` |
-| Navigation | `references/operation-patterns.md#navigation` |
-| Waiting | `references/operation-patterns.md#wait` |
-| Extraction | `references/operation-patterns.md#extraction` |
-| Batch | `references/operation-patterns.md#batch` |
-| Fallback | `references/fallback-operations.md` |
-| Tabs and sessions | `references/session-and-tabs.md` |
-| Debug evidence | `references/debugging-and-evidence.md` |
-| Network/API capture | `references/debugging-and-evidence.md#network-capture` |
-| Commands | `references/command-reference.md` |
-| Anti-patterns | `references/anti-patterns.md` |
-
-## Runtime First
-
-Before troubleshooting browser behavior, check runtime state:
-
-```bash
-omnibot doctor
-omnibot tabs
-omnibot visibility status
-omnibot browser current
-omnibot license status
-```
-
-If the extension is not connected, open Chrome or Edge with the omnibot extension loaded and keep an HTTP/HTTPS tab open.
-
-## Site Memory Reuse
-
-Before operating a complex site, check whether a generated site skill is installed for the current domain.
-
-1. Run `omnibot skills list-sites` to see available generated site skills.
-2. If a matching site skill is installed (e.g., `omnibot-xhs`), read its `SKILL.md` and use it for the operation.
-3. If no matching site skill is installed, create one with:
-   ```bash
-   omnibot explore run <url> --name <site> --goal "<explicit goal>"
-   omnibot skills install --agent opencode --site <site>
-   ```
-4. Generated site skills are not auto-loaded from `~/.omnibot/skills/`; they must be installed into the current agent's skill directory.
-
-## Generated Site Skill Installation
-
-Generated site skills are stored under `~/.omnibot/skills/omnibot-<name>/` but must be installed into each agent's native skill path to be auto-loaded.
-
-List available generated site skills:
-
-```bash
-omnibot skills list-sites
-```
-
-Install one generated site skill:
-
-```bash
-omnibot skills install --agent opencode --site xhs
-omnibot skills install --agent claude --site xhs
-omnibot skills install --agent codex --site xhs
-```
-
-Install all generated site skills:
-
-```bash
-omnibot skills install --agent opencode --all-sites
-```
-
-Default `omnibot skills install --agent <agent>` installs only the official packaged omnibot skill, not generated site skills.
-
-Local site memory is reusable strategy, not user task output. Do not write user inputs, scraped records, or private task results into generated site packages.
-
-## Fallback Discipline
-
-Fallback tiers are for completing operations after better patterns fail. They are not debugging shortcuts.
-
-Tier order:
-
-1. Semantic `find`.
-2. `snapshot -i` refs.
-3. Selectors.
-4. `dom` fallback.
-5. `mouse` fallback.
-6. `execute-js` fallback.
-7. Raw `cdp` fallback.
-
-When entering a lower tier, state why the higher tier failed. After any fallback action, verify with `snapshot`, `get`, `is`, `wait`, or equivalent evidence.
-
-## Debug Evidence
-
-Debugging is for evidence. Fallback is for completing operations.
-
-Use screenshots, annotated screenshots, console logs, network logs, trace, record/replay, and CDP inspection to explain failures or prove state. Do not treat `execute-js` as ordinary debug output.
-
-## Absolute Prohibitions
-
-- 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`, `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.
-
-See `references/anti-patterns.md` before using shortcuts.