@omniaibot/win-x64 1.1.0 → 1.1.2

package/bin/omnibot-windows-x64/VERSION

@@ -1 +1 @@
-1.1.0
+1.1.2

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

@@ -44,7 +44,7 @@ Every page-state workflow must use both controls:
 
 They are not substitutes. Session controls which workflow owns state. Tab ID controls which page receives the command.
 
-Do not rely on `switch-tab`, default tab, active tab, current tab, or prior targeting state for multi-step workflows.
+Do not rely on default tab, active tab, current tab, or prior targeting state. Every page command requires explicit `--tab-id`.
 
 Use the same token inside one workflow. Use different tokens for independent workflows.
 
@@ -108,6 +108,19 @@ Start from the task, not the command name. Use operation patterns for read, clic
 
 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 Scan 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 the current viewport before deciding what to do next | `scan --json` | Returns structured viewport state useful 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 `scan` as a long-form reader. Do not use `read` as the first step for click/fill workflows unless the user explicitly asked for page content first.
+
 ## Quick Routing
 
 | Need | Read |
@@ -168,6 +181,9 @@ 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, `switch-tab` for workflow state, or shell sleep instead of `omnibot wait`.
+- 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 `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.

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

@@ -6,16 +6,22 @@
 | Missing `--tab-id` | The command may target the wrong page. | Pass `--tab-id <TAB_ID>` on every page-state command. |
 | `execute-js` first | JavaScript bypasses standard browser interaction and hides better evidence. | Try semantic find, snapshot refs, selectors, DOM, and mouse first. |
 | Reusing `@eN` across tabs | Refs are tab-scoped and may point to a different element elsewhere. | Take a fresh `snapshot -i --tab-id <TAB_ID>` per tab. |
-| Relying on `switch-tab` | It creates implicit state and is unsafe for concurrent workflows. | Use explicit `--tab-id` on every command. |
+| Relying on implicit tab targeting | It is unavailable and unsafe for concurrent workflows. | Use explicit `--tab-id` on every page-state command. |
 | Using sleep instead of wait | Fixed sleeps are flaky and either too short or too slow. | Use `omnibot wait --text`, `--url`, selector state, load state, or `--fn`. |
 | Acting without verify | Command success is not task success. | Run `snapshot`, `get`, `is`, or `wait` after every action. |
 | Claiming success without evidence | The browser may not have changed as expected. | Cite verified URL, text, element state, screenshot, console, or network evidence. |
 | Raw CSS before semantic find | CSS is more brittle and less tied to user intent. | Start with `find role/text/label/placeholder/testid`. |
-| Screenshot when text extraction is enough | Screenshots cost more and are harder to parse. | Use `get text`, `scan --json`, or `full-scan --text-only`. |
+| Screenshot when text extraction is enough | Screenshots cost more and are harder to parse. | Use `read` for page content or `get text` for a selector. |
+| Using `scan` for long-form reading | `scan` is viewport observation and may miss long/lazy content. | Use `read --screens N --tab-id <TAB_ID>`. |
+| Using `read` before an action workflow | `read` returns text, not stable action targets. | Use `find`, `snapshot -i`, `get`, or `is` for click/fill/verify workflows. |
 | Headless expecting existing user login | Headless does not automatically share the user's visible browser session. | Use visible/background mode for existing login or explicitly log in headless. |
 | Mixing multiple workflows in one session token | Agents can overwrite each other's default state. | Use different tokens: `research`, `checkout`, `debug`. |
-| Using default tab state in concurrent agents | Active/current tab can change outside the workflow. | Discover or create a tab, save its id, and pass `--tab-id`. |
+| Using default tab state in concurrent agents | There is no default tab. Every page command requires explicit `--tab-id`. | Discover or create a tab, save its id, and pass `--tab-id`. |
 | Not checking doctor/tabs before troubleshooting | You may debug page logic when the runtime is disconnected. | Run `omnibot doctor` and `omnibot tabs` first. |
+| Using `tabs[0]` or the first tab | The first tab is often a user tab or the transport tab, not the workflow target. | Create or identify the intended tab and store its full id. |
+| Treating transport as target | Extension routing may use a different tab than the page being acted on. | Always pass `--tab-id <TAB_ID>` and verify with `get url --tab-id <TAB_ID>`. |
+| Closing discovered user tabs | Cleanup can destroy the user's real work. | Track only tool-created tabs and close only those ids. |
+| Leaving worker-token tabs untracked | Cross-token test tabs can remain open or auto-close later. | Add every worker-created tab id to cleanup tracking. |
 
 ## Red Flags
 

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

@@ -15,6 +15,47 @@ omnibot doctor
 Preferred pattern: See `runtime-and-status.md#startup-check`.
 Fallback relation: Not a fallback command.
 
+### status
+
+Purpose: Show daemon status only (lighter than `doctor`).
+
+```bash
+omnibot status
+```
+
+Preferred pattern: See `runtime-and-status.md#daemon-lifecycle`.
+Fallback relation: Not a fallback command.
+
+### start
+
+Purpose: Start the daemon in the background.
+
+```bash
+omnibot start
+```
+
+Equivalent to: `omnibot daemon start`
+
+### stop
+
+Purpose: Stop the running daemon.
+
+```bash
+omnibot stop
+```
+
+Equivalent to: `omnibot daemon stop`
+
+### run
+
+Purpose: Run the daemon in the foreground.
+
+```bash
+omnibot run
+```
+
+Equivalent to: `omnibot daemon run`
+
 ### tabs
 
 Purpose: List connected browser tabs and discover tab ids.
@@ -41,7 +82,7 @@ Fallback relation: Not a fallback command.
 
 ### scan
 
-Purpose: Read current rendered viewport, optionally as JSON.
+Purpose: Observe the current rendered viewport, especially before choosing a follow-up action.
 
 ```bash
 OMNIBOT_SESSION_TOKEN=research omnibot scan --json --tab-id <TAB_ID>
@@ -49,18 +90,20 @@ OMNIBOT_SESSION_TOKEN=research omnibot scan --text-only --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#read` and `operation-patterns.md#extraction`.
-Fallback relation: Before `full-scan`, `dom visible`, or `execute-js`.
+Fallback relation: Use before `dom visible` or `execute-js` when structured viewport state is needed. Use `read` instead for long-form page text.
 
-### full-scan
+### read
 
-Purpose: Scroll and read more page content, including lazy-loaded content.
+Purpose: Read clean rendered page text/Markdown from an existing tab or a temporary URL tab.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot full-scan --duration 5 --text-only --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
+OMNIBOT_SESSION_TOKEN=research omnibot read --json --screens 5 --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#read` and `operation-patterns.md#extraction`.
-Fallback relation: Use after targeted `get`, `is`, or `scan` are insufficient.
+Fallback relation: Prefer for page content. Use `scan --json` when the next step is action planning, and `snapshot -i` when actionable refs are needed.
 
 ### snapshot -i
 
@@ -360,27 +403,21 @@ Purpose: Manage browser tabs.
 ```bash
 OMNIBOT_SESSION_TOKEN=research omnibot tab list
 OMNIBOT_SESSION_TOKEN=research omnibot tab new https://docs.example.com --label docs
-OMNIBOT_SESSION_TOKEN=research omnibot tab switch docs
 OMNIBOT_SESSION_TOKEN=research omnibot tab close docs
 ```
 
 Preferred pattern: See `session-and-tabs.md#tab-explicit`.
-Fallback relation: `tab switch` is casual only; do not use it as workflow state.
+Removed: `tab switch` and `tab focus` are no longer available. Use explicit `--tab-id` on every page-state command.
 
-### window / frame / switch-tab / focus-tab
+### window / frame
 
-Purpose: Manage windows, frames, and visible browser focus.
+Purpose: Manage windows and frames.
 
 ```bash
 OMNIBOT_SESSION_TOKEN=research omnibot window new
 OMNIBOT_SESSION_TOKEN=research omnibot frame main
-OMNIBOT_SESSION_TOKEN=research omnibot switch-tab 123
-OMNIBOT_SESSION_TOKEN=research omnibot focus-tab 123
 ```
 
-Preferred pattern: See `session-and-tabs.md#switch-tab` and `session-and-tabs.md#focus-tab`.
-Fallback relation: `focus-tab` is for user-visible UI, not targeting reliability.
-
 ## Waiting & Batch
 
 ### wait

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

@@ -106,7 +106,7 @@ Use `execute-js` only when:
 - CSS selector operation fails.
 - DOM fallback fails.
 - A complex frontend event must be triggered.
-- Runtime state cannot be read through `scan`, `full-scan`, `get`, or `is`.
+- Runtime state cannot be read through `read`, `scan`, `get`, or `is`.
 
 Read-only JavaScript fallback:
 

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

@@ -6,24 +6,26 @@ 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 scan when the agent needs a structured current-viewport observation 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.
+6. `scan --json` only when the next step depends on current viewport structure.
+7. `snapshot -i` when actionable refs are needed.
+8. `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 +33,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`, targeted reads, or scan omit needed runtime state, go to `fallback-operations.md#fallback-tier-model`. Start with DOM fallback before JavaScript.
 
 ## Click
 
@@ -221,7 +224,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
 
@@ -273,8 +276,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. `scan --json` for structured viewport extraction before action planning.
 4. `assets list/export` for resources.
 5. `clipboard read` only when clipboard content is part of the task.
 
@@ -289,17 +292,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`, `scan`, and `get` could not access it.
 
 ## Upload
 

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.2",
   "description": "omnibot executable for Windows x64",
   "os": [
     "win32"