@omniaibot/win-x64 1.1.0 → 1.1.6

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

@@ -6,24 +6,25 @@ Use this file to choose behavior by task. Every page-state workflow must set `OM
 
 ### When to use
 
-Use Read when the agent needs current browser state, page text, a single value, visibility, enabled/checked state, layout box, or computed styles.
+Use Read when the agent needs clean rendered page content: article text, search results, feed items, long pages, lazy-loaded text, or a human-readable summary source.
+
+Use targeted state commands when the agent needs one value, visibility, enabled/checked state, layout box, or computed styles. Use `snapshot -i` when the agent needs current visible UI structure for deciding the next action.
 
 ### Preferred sequence
 
-1. `get title/url/text/html/value/attr/count/box/styles`
-2. `is visible/enabled/checked`
-3. `scan --json`
-4. `full-scan`
-5. `snapshot -i`
-6. `dom visible`
-7. `execute-js` fallback
+1. `read --tab-id <TAB_ID>` for clean page text on an existing tab.
+2. `read --screens N --tab-id <TAB_ID>` for longer or lazy-loaded pages.
+3. `read <URL>` when opening a temporary tab only for reading that URL.
+4. `get title/url/text/html/value/attr/count/box/styles` for narrow evidence.
+5. `is visible/enabled/checked` for boolean state.
+5. `snapshot -i` when actionable refs are needed.
+6. `dom visible` or `execute-js` fallback only after standard reads cannot access the state.
 
 ### Example
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot get title --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=research omnibot get url --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=research omnibot get text "#main" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot read --screens 5 --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot read --screens 3 https://example.com/article
 ```
 
 ### Verification
@@ -31,13 +32,14 @@ OMNIBOT_SESSION_TOKEN=research omnibot get text "#main" --tab-id <TAB_ID>
 Use the narrowest read that proves the claim:
 
 ```bash
+OMNIBOT_SESSION_TOKEN=research omnibot get title --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot is visible "#main" --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot get count ".result" --tab-id <TAB_ID>
 ```
 
 ### Fallback entry point
 
-If targeted reads fail or omit needed runtime state, go to `fallback-operations.md#fallback-tier-model`. Start with DOM fallback before JavaScript.
+If `read` or targeted reads omit needed runtime state, go to `fallback-operations.md#fallback-tier-model`. Start with DOM fallback before JavaScript.
 
 ## Click
 
@@ -158,9 +160,23 @@ OMNIBOT_SESSION_TOKEN=form omnibot is checked "#agree" --tab-id <TAB_ID>
 
 For checkboxes, verify boolean state. For selects, verify value or dependent page state.
 
+### CSS-only dropdowns and custom menus
+
+Some dropdowns, hover menus, tooltips, and custom selects are CSS-only widgets. The visible trigger may be accessible, while the option nodes are hidden `<div>` elements without `role`, accessible name, or stable refs.
+
+Use this evidence path before JavaScript:
+
+1. Try semantic `find` or a normal `select`/`click` against the trigger.
+2. Verify whether the selected label, result order, or dependent state changed.
+3. Run `snapshot -i` after opening the control.
+4. If the trigger clicked but options are absent from the accessibility tree, do not keep retrying `find` or stale refs.
+5. Escalate to `fallback-operations.md#css-only-dropdown-javascript-fallback` for an atomic open-then-select script.
+
+`snapshot -i` not showing an option does not prove the DOM node is missing. It may only prove the widget is not exposed through the accessibility tree.
+
 ### Fallback entry point
 
-If native select/check fails, use `fallback-operations.md#selector-fallback`, then JavaScript only if events must be synthesized.
+If native select/check fails, use `fallback-operations.md#selector-fallback`. Use JavaScript only if events must be synthesized or if evidence shows a CSS-only multi-step widget cannot be completed through semantic, snapshot, selector, DOM, or mouse tiers.
 
 ## Navigation
 
@@ -221,7 +237,7 @@ OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
 
 ### Fallback entry point
 
-`switch-tab` cannot be used as a reliable base for multi-step workflows. Use it only for casual single-step work. If targeted same-tab navigation is unavailable, state the limitation, re-observe the tab list, and verify before continuing.
+Same-tab navigation must include `--tab-id <TAB_ID>`. If the target tab id is unknown, run `omnibot tabs` first and choose the intended tab explicitly.
 
 ## Wait
 
@@ -258,7 +274,7 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot wait --fn "window.appReady === true" --ta
 
 ### Verification
 
-After waiting, read the final condition with `get`, `is`, `scan`, or `snapshot`.
+After waiting, read the final condition with `get`, `is`, `wait`, or `snapshot`.
 
 ### Fallback entry point
 
@@ -273,8 +289,8 @@ Use Extraction for retrieving page text, HTML fragments, links, counts, assets,
 ### Preferred sequence
 
 1. `get text/html/attr/count` for targeted extraction.
-2. `scan --json` for structured viewport extraction.
-3. `full-scan` for long or lazy pages.
+2. `read --screens N` for clean page text, long pages, or lazy-loaded content.
+3. `snapshot -i` for structured page observation before action planning.
 4. `assets list/export` for resources.
 5. `clipboard read` only when clipboard content is part of the task.
 
@@ -289,17 +305,17 @@ OMNIBOT_SESSION_TOKEN=extract omnibot get count ".result" --tab-id <TAB_ID>
 Long page example:
 
 ```bash
-OMNIBOT_SESSION_TOKEN=extract omnibot full-scan --duration 5 --text-only --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=extract omnibot read --screens 5 --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=extract omnibot assets list --tab-id <TAB_ID>
 ```
 
 ### Verification
 
-Verify extraction completeness with count, repeated scan after scroll, or targeted reads for expected markers.
+Verify extraction completeness with expected markers in `read`, element counts, or targeted reads for known selectors.
 
 ### Fallback entry point
 
-If content exists only in runtime objects, use `fallback-operations.md#javascript-fallback` after explaining why `scan`, `full-scan`, and `get` could not access it.
+If content exists only in runtime objects, use `fallback-operations.md#javascript-fallback` after explaining why `read`, `snapshot`, and `get` could not access it.
 
 ## Upload
 
@@ -349,7 +365,7 @@ Use Batch for short, known-safe command chains where the target tab and verifica
 ### Example
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"scan"},{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
+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>
 ```
 

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/runtime-and-status.md

@@ -8,6 +8,7 @@ Run this sequence before diagnosing browser failures:
 
 ```bash
 omnibot doctor
+omnibot status
 omnibot tabs
 omnibot visibility status
 omnibot browser current
@@ -17,6 +18,7 @@ omnibot license status
 Interpretation:
 
 - `doctor` checks daemon and extension health.
+- `status` checks daemon status only (lighter than `doctor`).
 - `tabs` proves connected tabs are visible and provides tab ids.
 - `visibility status` shows whether automation is visible, background, dedicated-profile, or headless.
 - `browser current` shows current browser runtime ownership.
@@ -24,6 +26,26 @@ Interpretation:
 
 If the extension is not connected, open Chrome or Edge with the omnibot extension loaded and keep an HTTP/HTTPS page open.
 
+## Daemon Lifecycle
+
+Top-level shortcuts:
+
+```bash
+omnibot status   # Show daemon status
+omnibot start    # Start the daemon
+omnibot stop     # Stop the daemon
+omnibot run      # Run daemon in foreground
+```
+
+Full form (also supported):
+
+```bash
+omnibot daemon run
+omnibot daemon start
+omnibot daemon stop
+omnibot daemon status
+```
+
 ## doctor
 
 ```bash

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/session-and-tabs.md

@@ -25,6 +25,47 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot get url --tab-id <TAB_ID>
 
 Do not rely on default tab, active tab, current tab, or previous targeting state.
 
+## Explicit Targeting Model
+
+Page-state commands never infer a target tab. Always pass `--tab-id <TAB_ID>` for commands that read or mutate page state.
+
+Transport selection is internal. Omnibot may use any connected extension WebSocket to deliver extension-level commands, but that transport tab is never the page target.
+
+Do not use the first returned tab, `tabs[0]`, browser active tab, newest tab, or prior command state as a target.
+
+## Transport Is Not Target
+
+Omnibot can send extension commands through any connected extension WebSocket tab. That transport tab is not the page target. The target is only the tab id passed in the command, for example `--tab-id edge-client:123`.
+
+Safe sequence:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot navigate https://example.com
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id edge-client:123
+OMNIBOT_SESSION_TOKEN=research omnibot click --tab-id edge-client:123 @e4
+OMNIBOT_SESSION_TOKEN=research omnibot wait --text "Saved" --tab-id edge-client:123
+```
+
+Unsafe sequence:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot tabs
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i
+```
+
+The unsafe sequence has no target. Do not infer target from first tab, active tab, or prior operation.
+
+## Safe Browser Test Cleanup
+
+Browser integration tests must only close tabs they created:
+
+1. Record the list of existing tabs before creating fixtures.
+2. Create a unique fixture tab per case.
+3. Store the returned full tab id.
+4. Pass that id to every page-state command.
+5. Close only stored fixture ids in cleanup.
+6. Verify user tabs remain present after the test.
+
 ## Why Both
 
 - Session = workflow isolation.
@@ -80,36 +121,11 @@ OMNIBOT_SESSION_TOKEN=research omnibot get url --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
 ```
 
-## switch-tab
-
-`switch-tab` is only for casual single-step usage.
+## No Implicit Targeting
 
-Do not build a multi-step workflow on `switch-tab`. It creates implicit state and can be stale or crossed by concurrent agents.
+Omnibot does not provide a workflow-level current tab command. Every command that reads or changes page state must receive `--tab-id <TAB_ID>` in that command invocation.
 
-Bad:
-
-```bash
-OMNIBOT_SESSION_TOKEN=research omnibot switch-tab 123
-OMNIBOT_SESSION_TOKEN=research omnibot click @e4
-```
-
-Good:
-
-```bash
-OMNIBOT_SESSION_TOKEN=research omnibot click --tab-id 123 @e4
-OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id 123
-```
-
-## focus-tab
-
-Use `focus-tab` only when the user needs to see the browser UI.
-
-It is not a reliable targeting primitive for agent workflows.
-
-```bash
-OMNIBOT_SESSION_TOKEN=demo omnibot focus-tab 123
-OMNIBOT_SESSION_TOKEN=demo omnibot snapshot -i --tab-id 123
-```
+This prevents stale target state and cross-agent tab confusion.
 
 ## browser claim/release
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omniaibot/win-x64",
-  "version": "1.1.0",
+  "version": "1.1.6",
   "description": "omnibot executable for Windows x64",
   "os": [
     "win32"
@@ -15,9 +15,9 @@
     "bin/"
   ],
   "keywords": [
-    "mcp",
     "browser",
     "automation",
+    "agent",
     "omnibot"
   ],
   "author": "Unagi-cq",