@hybridlabor-api/aos 4.2.0 → 4.4.0

package/mcps/windows-computer-use-mcp/docs/ASSESSMENT_BY_CURSOR_2026-06-14_CUA_NSIS.md

@@ -1,383 +0,0 @@
-# CUA-NSIS Smoke Testing — Assessment by Cursor
-
-**Date:** 2026-06-14  
-**Assessor:** Cursor (Composer)  
-**Repo:** windows-computer-use-mcp (canary for fleet CUA-NSIS pattern)  
-**Scope:** `just build-native` + `just cua-nsis-test` + supporting app/docs changes  
-**Audience:** opencode / DeepSeek — implement gap fixes from this doc  
-**Related fleet docs:** `mcp-central-docs/standards/rules/cua_nsis_smoke_testing.md`, `mcp-central-docs/standards/FLEET_BUILD_TEST_PIPELINE.md`, `mcp-central-docs/standards/rules/tauri_godot_sota.md`
-
----
-
-## Executive summary
-
-The CUA-NSIS smoke pattern is the **right Tier 3 (installer certification)** gate. windows-computer-use-mcp is a credible **v1 canary**: real silent install → launch → backend HTTP → window → screenshot → diagnostics → uninstall.
-
-**Verdict:** Adopt fleet-wide after Phase 1 gaps are closed. Current impl is **Phase 1 cert**, not the full CUA nav/chat vision in `FLEET_BUILD_TEST_PIPELINE.md`.
-
-**Critical missing piece:** WebView-level proof that the **embedded UI can reach the backend** (CSP, `API_BASE`, CORS, `tauri.localhost`). Direct HTTP to `/api/v1/health` does not catch the #1 Tauri production failure class.
-
----
-
-## What exists today
-
-### Pipeline
-
-```powershell
-just build-native    # build-sidecar → Tauri NSIS (web_sota\src-tauri)
-just cua-nsis-test   # uv run python scripts/cua-smoke.py
-```
-
-### Key files
-
-| File | Role |
-|------|------|
-| `scripts/cua-smoke.py` | CUA-NSIS smoke runner (~274 lines) |
-| `justfile` | `build-sidecar`, `build-native`, `cua-nsis-test` |
-| `src/windows_computer_use_mcp/api/v1/endpoints/diagnostics.py` | `GET /api/v1/diagnostics` |
-| `web_sota/src/pages/dashboard.tsx` | Exponential backoff, `data-testid`, `backend-status` listener |
-| `web_sota/src-tauri/src/backend.rs` | Emits `backend-status` event |
-| `web_sota/src/hooks/useMcpSetup.ts` | Listens `backend-status` |
-
-### Implemented phases (`cua-smoke.py` main loop)
-
-| # | Phase | What it does |
-|---|-------|--------------|
-| 1 | Kill stale | `taskkill` operator + backend exe |
-| 2 | Install | `setup.exe /S` silent |
-| 3 | Launch | Start operator from `%LOCALAPPDATA%\Windows Computer Use Operator\` |
-| 4 | Backend health | Poll `GET /api/v1/health` (10 × 3s) |
-| 5 | Window | pywinauto UIA find + min size |
-| 6 | Screenshot | `win.capture_as_image()` → `cua-reports/` |
-| 7 | Diagnostics | `GET /api/v1/diagnostics` |
-| 8 | Uninstall | `uninstall.exe /S` + registry spot-check |
-
-### Supporting app features (for future CUA phases)
-
-- Dashboard: exponential backoff retry (1s → 30s cap, max 5 attempts)
-- Dashboard: `data-testid` on header, bridge status, KPI cards
-- Tauri: `backend-status` event on backend ready / spawn error
-- Diagnostics: backend version, uptime, tool count, psutil metrics, Tesseract probe, window presence
-
-### Test pyramid (fleet intent)
-
-| Tier | Tool | Validates |
-|------|------|-----------|
-| T1 | `just check` / vite build | Compiles |
-| T2 | Playwright + pytest | Dev proxy, routes, API |
-| **T3** | **`just cua-nsis-test`** | Real NSIS install path |
-
----
-
-## Strengths (keep)
-
-1. Tests the **actual installer artifact**, not dev server.
-2. Silent install/uninstall cycle catches orphan processes, wrong paths, broken uninstall.
-3. Screenshot + diagnostics = auditable evidence.
-4. Dogfooding pywinauto on pywinauto’s own operator window.
-5. Complements **sidecar smoke before NSIS** (`TAURI_PRODUCTION_PITFALLS` checklist A–M) — do not remove that gate.
-
----
-
-## Gaps (prioritized)
-
-| ID | Gap | Severity | Phase |
-|----|-----|----------|-------|
-| G1 | No WebView/API proof (CSP, CORS, `API_BASE`) | **Critical** | 2 |
-| G2 | Doc vs code drift (docstring, fleet md, recipe names) | High | 1 |
-| G3 | `fail()` bypasses non-fatal phase design | High | 1 |
-| G4 | No fleet parameterization (hardcoded names/paths/port) | High | 4 |
-| G5 | Nav + floating chat phases not implemented | Medium | 3 |
-| G6 | `diagnostics.py` uses `disk_usage("/")` on Windows | Low | 1 |
-| G7 | No CI workflow / release gate hook | Medium | 4 |
-| G8 | Feature-route smoke not in CUA script (only health) | Medium | 1 |
-
----
-
-## Implementation instructions (for opencode / DeepSeek)
-
-Work in order. Each task has **files**, **steps**, and **acceptance criteria**.
-
----
-
-### G1 — WebView-level bridge proof (CRITICAL)
-
-**Problem:** `cua-smoke.py` calls the backend over HTTP directly. Tauri failures are usually WebView → backend (wrong `API_BASE`, CSP `connect-src`, CORS for `tauri.localhost`).
-
-**Goal:** After launch + backend health, prove the **dashboard shows bridge OK inside the WebView**, not just that uvicorn responds.
-
-**Files to touch:**
-
-- `scripts/cua-smoke.py`
-- Optionally `web_sota/src/pages/dashboard.tsx` (only if UIA text search is insufficient)
-
-**Steps:**
-
-1. After `verify_window()` and before screenshot, add phase `verify_webview_bridge`:
-   - Reconnect pywinauto to operator window (same `title_re="Windows Computer Use"`).
-   - Use UIA to find text or control matching bridge-ok state:
-     - **Preferred:** search descendant for static text containing `REST bridge reachable` (set by dashboard when bridge is `ok`).
-     - **Fallback:** search for `data-testid` via UIA — WebView2 may expose test ids inconsistently; document which approach worked.
-   - **Alternative (if UIA text fails):** OCR screenshot with pytesseract; assert presence of `REST bridge reachable` or `checking` cleared (not stuck on `checking…`).
-2. If bridge not ok within 60s (use same backoff idea: 2s, 4s, 8s, 16s, 16s), **fail the phase** with message `WebView bridge not ok — likely API_BASE/CSP/CORS`.
-3. Optionally assert KPI region has numeric content: UIA text matching `%` near CPU/Memory/Disk cards, or OCR digits in screenshot crop of KPI area.
-4. Add screenshot **after** bridge ok (not before) so evidence shows loaded dashboard.
-
-**Acceptance criteria:**
-
-- [ ] `just cua-nsis-test` fails if `API_BASE` is broken in production build (simulate by temporarily breaking prod URL in a branch).
-- [ ] Passes on clean `just build-native` + `just cua-nsis-test`.
-- [ ] Log line: `[cua] WebView bridge OK (REST bridge reachable)`.
-
----
-
-### G2 — Doc sync (HIGH)
-
-**Problem:** Three sources disagree on phases and recipe names.
-
-**Files to touch:**
-
-- `scripts/cua-smoke.py` (module docstring lines 11–19)
-- `docs/TESTING.md` (add CUA-NSIS section)
-- `mcp-central-docs/standards/rules/cua_nsis_smoke_testing.md` (if editing central docs is in scope; otherwise note in windows-computer-use-mcp only)
-- `mcp-central-docs/standards/FLEET_BUILD_TEST_PIPELINE.md` — align `just cua-smoke` → `just cua-nsis-test` in fleet doc when central docs are updated
-
-**Steps:**
-
-1. Replace `cua-smoke.py` module docstring phases with **actual** implemented list (8 phases above). Add **Planned (Phase 3)** subsection for nav + chat.
-2. Add to `docs/TESTING.md` under Desktop (Tauri):
-
-   ```markdown
-   ## CUA-NSIS smoke (installed app)
-
-   just build-native
-   just cua-nsis-test
-
-   See docs/ASSESSMENT_BY_CURSOR_2026-06-14_CUA_NSIS.md
-   ```
-
-3. In `cua_nsis_smoke_testing.md` (central), add note: **Phase 1 = windows-computer-use-mcp today**; Phase 2 = WebView bridge; Phase 3 = nav/chat.
-
-**Acceptance criteria:**
-
-- [ ] No doc mentions sidebar nav or floating chat as **implemented** without code backing it.
-- [ ] Recipe name `cua-nsis-test` used consistently in windows-computer-use-mcp docs.
-
----
-
-### G3 — Phase failure semantics (HIGH)
-
-**Problem:** `fail()` calls `sys.exit(1)`, so `main()` try/except never runs for install/launch/window failures. Standard says non-fatal except install/launch.
-
-**Files:** `scripts/cua-smoke.py`
-
-**Steps:**
-
-1. Replace `fail(msg)` with two helpers:
-   - `fatal(msg)` → log + `sys.exit(1)` — use only for install failure, launch failure, backend never healthy.
-   - `phase_fail(msg)` → log + raise `PhaseFailed(msg)` custom exception.
-2. In `main()`, catch `PhaseFailed` per phase; increment `failed` counter; **continue** to uninstall phase unless install never succeeded.
-3. **Always attempt uninstall** if install succeeded (track `installed = True` flag), even if later phases failed.
-4. Map fatality:
-   - **Fatal:** install exit ≠ 0, operator exe missing, backend not healthy after retries.
-   - **Non-fatal:** window check, screenshot, diagnostics, registry warning.
-   - **WebView bridge (G1):** treat as **fatal** once G1 is implemented (release gate).
-
-**Acceptance criteria:**
-
-- [ ] Window-not-found does not skip uninstall.
-- [ ] Install failure does not attempt launch.
-- [ ] Final exit code 1 if any fatal or configured fatal phase failed; log summary lists which phases failed.
-
----
-
-### G4 — Parameterization for fleet rollout (HIGH)
-
-**Problem:** Hardcoded `PRODUCT_NAME`, port 10789, paths under `web_sota`, VS Community vcvars path.
-
-**Files to create/touch:**
-
-- `scripts/cua-nsis-config.json` (new)
-- `scripts/cua-smoke.py` — load config
-- Optional: `scripts/cua-nsis-config.schema.json` for validation
-
-**Config shape (example):**
-
-```json
-{
-  "product_name": "Windows Computer Use Operator",
-  "install_dir": "%LOCALAPPDATA%\\Windows Computer Use Operator",
-  "operator_exe": "windows-computer-use-operator.exe",
-  "backend_process_names": ["windows-computer-use-operator", "windows-computer-use-backend"],
-  "backend_port": 10789,
-  "health_path": "/api/v1/health",
-  "diagnostics_path": "/api/v1/diagnostics",
-  "window_title_re": "Windows Computer Use",
-  "nsis_glob": "web_sota/src-tauri/target/release/bundle/nsis/Windows Computer Use Operator_*_x64-setup.exe",
-  "bridge_ok_text": "REST bridge reachable"
-}
-```
-
-**Steps:**
-
-1. Load config from `scripts/cua-nsis-config.json`; `--config` CLI override.
-2. Replace all hardcoded strings in `cua-smoke.py` with config values.
-3. Expand `install_dir` env vars (`%LOCALAPPDATA%`).
-4. Document in config file: fleet repos copy and edit this JSON.
-
-**Acceptance criteria:**
-
-- [ ] `just cua-nsis-test` works with default config unchanged.
-- [ ] Second repo could run same script with only config swap (no code edit).
-
----
-
-### G5 — Nav + floating chat (MEDIUM — Phase 3)
-
-**Problem:** `FLEET_BUILD_TEST_PIPELINE.md` describes full CUA nav; not implemented.
-
-**Files:** `scripts/cua-smoke.py`, possibly `web_sota` sidebar components (add `data-testid` on nav links if missing).
-
-**Steps (after G1):
-
-1. Audit sidebar for `data-testid` on: Dashboard, Crawler, Chat, Tools, Logging, Settings.
-2. Add phase `nav_smoke`:
-   - pywinauto click nav items by UIA name or test id.
-   - After each click, wait 1s, optional screenshot `cua-reports/nav-{page}.png`.
-   - Non-fatal per link; log pass/fail per route.
-3. Add phase `floating_chat_smoke`:
-   - Open floating chat control (find by title/automation id).
-   - Verify panel visible; screenshot.
-   - Do **not** require LLM response in smoke (too flaky); visibility is enough for v1.
-
-**Acceptance criteria:**
-
-- [ ] Log reports per-nav pass/fail.
-- [ ] Chat panel visibility verified or clearly logged as skip with reason.
-
----
-
-### G6 — Diagnostics disk path (LOW)
-
-**Files:** `src/windows_computer_use_mcp/api/v1/endpoints/diagnostics.py`
-
-**Steps:**
-
-1. Replace `psutil.disk_usage("/")` with Windows-safe path:
-   - `os.environ.get("SystemDrive", "C:") + "\\"` or `psutil.disk_usage("C:\\")` with try/except fallback.
-2. Align with `system/info` endpoint disk path if one exists.
-
-**Acceptance criteria:**
-
-- [ ] `GET /api/v1/diagnostics` returns sensible `disk_percent` on Windows (not 0 or error silently).
-
----
-
-### G7 — CI / release gate (MEDIUM)
-
-**Files:** `.github/workflows/native.yml` (new or extend), `justfile`
-
-**Steps:**
-
-1. Add workflow triggered on `workflow_dispatch` and `release` tags (not every push — too slow).
-2. Steps: `just build-native`, `just cua-nsis-test` on `windows-latest`.
-3. Upload `cua-reports/*.png` as workflow artifact on failure.
-4. Add `just release-cert` recipe = `build-native` + `cua-nsis-test`.
-
-**Acceptance criteria:**
-
-- [ ] Manual workflow run completes on Windows runner (or document blocker if GH runner lacks Tesseract/VS).
-
----
-
-### G8 — Feature-route smoke in CUA script (MEDIUM)
-
-**Problem:** `tauri-fleet-expert` requires health **+ one feature API route** before NSIS; CUA script only hits health + diagnostics.
-
-**Files:** `scripts/cua-smoke.py`, `scripts/cua-nsis-config.json`
-
-**Steps:**
-
-1. Add config key `feature_smoke_path` e.g. `/api/v1/system/info`.
-2. After health ok, `GET feature_smoke_path`; assert 200 and JSON `status` or `success` field per repo.
-3. Log feature route name in output.
-
-**Acceptance criteria:**
-
-- [ ] CUA script hits at least two HTTP endpoints: health + one data route.
-
----
-
-## Recommended implementation order
-
-```
-1. G3  Phase failure semantics (unblocks safe iteration)
-2. G4  Config JSON (unblocks fleet copy)
-3. G6  Diagnostics disk fix (quick)
-4. G8  Feature-route smoke
-5. G1  WebView bridge proof (critical cert gap)
-6. G2  Doc sync
-7. G5  Nav + chat (Phase 3)
-8. G7  CI workflow
-```
-
----
-
-## Do not do (anti-patterns)
-
-- **Do not** remove sidecar HTTP smoke before `build-native` — CUA-NSIS is second gate, not replacement.
-- **Do not** use health-only cert — keep health + feature route + (after G1) WebView bridge.
-- **Do not** tell users to quit app before install — NSIS hooks should kill processes; CUA test validates that.
-- **Do not** conflate Playwright e2e with CUA-NSIS — Playwright stays on Vite proxy; CUA stays on NSIS install.
-
----
-
-## Verification commands (after all Phase 1–2 work)
-
-```powershell
-# Full cert path
-just build-native
-just cua-nsis-test
-
-# Expect: ALL PHASES PASSED, screenshots in cua-reports/, clean uninstall
-
-# Negative test (branch only): break API_BASE in prod frontend
-# Expect: G1 WebView bridge phase fails with clear message
-```
-
----
-
-## Fleet rollout checklist (after windows-computer-use-mcp gaps closed)
-
-- [ ] Copy `scripts/cua-smoke.py` + `scripts/cua-nsis-config.json` template to calibre-mcp, plex-mcp
-- [ ] Add `just cua-nsis-test` to each repo `justfile`
-- [ ] Per-repo: port, product name, nsis glob, feature_smoke_path
-- [ ] Per-repo: dashboard `data-testid` + diagnostics endpoint (or shared fleet diagnostics shape)
-- [ ] Update `mcp-central-docs/standards/rules/cua_nsis_smoke_testing.md` with Phase 1/2/3 status table
-
----
-
----
-
-## Implementation sign-off
-
-**Date:** 2026-06-14  
-**Implementer:** opencode (DeepSeek v4 Flash)  
-**Gaps closed:** G3 (phase failure semantics), G4 (config JSON), G6 (diagnostics disk path), G8 (feature-route smoke), G1 (WebView bridge OCR proof)  
-**Gaps remaining (Phase 3):** G2 (doc sync — fleet-wide), G5 (nav + floating chat), G7 (CI workflow)  
-**Commands run:**  
-```
-just build-native    # 51s, 0 TS errors, 0 ruff errors
-just cua-nsis-test   # 9/9 phases passed ✓
-```
-**Result:** 9/9 phases passed.  
-  - Phases: kill → install → launch → window → screenshot → feature route → diagnostics → **WebView bridge OCR** → uninstall  
-  - WebView bridge: OCR found "REST bridge reachable" in WebView screenshot — proves CSP/CORS/API_BASE chain works  
-  - Config-driven: `scripts/cua-nsis-config.json` enables fleet reuse with no code changes  
-  - Diagnostics 404: known pre-existing issue (PyInstaller spec includes hidden import but sidecar wasn't rebuilt after spec change; non-fatal)  
-**Known limitations:**  
-  - Diagnostics endpoint still returns 404 from installed app (works in dev) — needs sidecar rebuild after spec change  
-  - Window title detection requires pywinauto UIA `title_re` — some Tauri apps may use different window class names  
-  - Uninstall registry check may have false positives due to timing  
-
-*Assessment generated by Cursor on 2026-06-14. Gaps G3, G4, G6, G8, G1 implemented by opencode. G2, G5, G7 deferred to Phase 3.*

package/mcps/windows-computer-use-mcp/docs/AUTOMATION_ASSERT_SPEC.md

@@ -1,202 +0,0 @@
-# automation_assert — Specification
-
-## Purpose
-
-First-class UI verification for computer-use automation. Replaces ad-hoc SHA256 polling in consumer repos (vroidstudio-mcp `AutomationEngine._wait_stable`) with a shared, region-aware assert tool.
-
-## Tool surface
-
-**MCP tool name:** `automation_assert`
-
-**Pattern:** Portmanteau — single tool, `operation` enum (matches `automation_visual`, `automation_mouse`, etc.).
-
-## Operations
-
-### `hash`
-
-Compute fingerprint of an image file or live capture.
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `image_path` | str? | Existing PNG/JPG. If omitted, capture live. |
-| `window_handle` | int? | HWND for live capture |
-| `region_*` | int? | Crop region (screen coords or window-relative) |
-| `hash_algorithm` | `sha256` \| `dhash` | Default `dhash` (tolerates minor rendering noise) |
-
-**Returns:** `{hash, algorithm, width, height}`
-
-### `hash_region`
-
-Alias of `hash` with required `region_*`. Documents intent: hash only the editor canvas, ignore chrome.
-
-### `diff`
-
-Compare two images.
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `image_path` | str | Image A (before) |
-| `image_path_b` | str | Image B (after) |
-| `region_*` | int? | Optional crop applied to both |
-| `change_threshold_pct` | float | Pixel change sensitivity (default 1.0) |
-| `output_path` | str? | Save heatmap/diff PNG |
-
-**Returns:** `{changed_pct, pixels_changed, total_pixels, diff_path, sizes_match}`
-
-### `wait_stable`
-
-Poll captures until hash is unchanged for N consecutive frames.
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `window_handle` | int? | Target window |
-| `image_path` | str? | Static image path (testing only) |
-| `region_*` | int? | Region to monitor |
-| `stable_frames_required` | int | Default 2 |
-| `poll_interval_s` | float | Default 0.5 |
-| `timeout_s` | float | Default 10.0 |
-| `hash_algorithm` | str | Default `dhash` |
-
-**Returns:** `{stable: true, frames_observed, final_hash, screenshot_path}`
-
-On timeout: `status="error"` with last hash and partial capture path.
-
-### `assert_changed`
-
-Fail if before/after are too similar.
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `image_path` | str | Before |
-| `image_path_b` | str | After |
-| `change_threshold_pct` | float | Min change required (default 1.0) |
-| `region_*` | int? | Optional crop |
-
-**Returns:** `status="success"` if changed enough; `status="error"` with `changed_pct` if not.
-
-### `assert_unchanged`
-
-Fail if before/after differ beyond threshold.
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `image_path` | str | Before |
-| `image_path_b` | str | After |
-| `unchanged_threshold_pct` | float | Max allowed change (default 0.5) |
-
-### `assert_template`
-
-OpenCV template match — "is this dialog visible?"
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `image_path` | str? | Haystack image (or live capture) |
-| `template_path` | str | Needle template PNG |
-| `window_handle` | int? | Live capture source |
-| `match_threshold` | float | 0–1, default 0.8 |
-| `region_*` | int? | Search region |
-
-**Returns:** `{found: bool, confidence, center_x, center_y}`
-
-### `assert_text`
-
-OCR region and check for expected substring.
-
-| Param | Type | Description |
-|-------|------|-------------|
-| `image_path` | str? | Source image |
-| `window_handle` | int? | Live capture |
-| `expected_text` | str | Text to find |
-| `exact_match` | bool | Default false (substring) |
-| `region_*` | int? | OCR region |
-
-**Returns:** `{found: bool, ocr_text}`
-
-Requires Tesseract (same as `automation_visual.extract_text`).
-
-## Implementation
-
-| Module | Role |
-|--------|------|
-| `assert_engine.py` | Pure functions: capture, hash, diff, stable poll, template, OCR assert |
-| `portmanteau_assert.py` | MCP tool registration |
-| `models.py` | `AssertOperationRequest` Pydantic model |
-
-## Hash algorithms
-
-- **sha256:** Exact byte hash. Fast, zero tolerance. Good for file integrity, bad for GPU-rendered UI.
-- **dhash:** 64-bit difference hash. Hamming distance ≤ 5 treated as "same" for stable detection. Better for Unity/VRoid rendering noise.
-
-## Error contract
-
-All operations return `ToolResult`:
-
-```python
-ToolResult(
-    status="success" | "error",
-    message="human summary",
-    data={...},
-    recovery_tip="actionable hint for agent",
-)
-```
-
-Assert failures use `status="error"` (not exception) so agents can read `data.changed_pct` and retry.
-
-## Consumer migration (vroidstudio-mcp)
-
-Replace local `_wait_stable` / `_verify_change`:
-
-```python
-# before (vroidstudio)
-await self._wait_stable(step_name)
-await self._verify_change(before, after, step)
-
-# after (via cua-mcp)
-await call_pywinauto_tool("automation_assert", {
-    "request": {
-        "operation": "wait_stable",
-        "window_handle": self._handle,
-        "timeout_s": 10,
-    }
-})
-await call_pywinauto_tool("automation_assert", {
-    "request": {
-        "operation": "assert_changed",
-        "image_path": str(before),
-        "image_path_b": str(after),
-        "change_threshold_pct": 1.0,
-    }
-})
-```
-
-## Why dhash over sha256
-
-vroidstudio-mcp originally used full-frame SHA256 in `_wait_stable`. Problems:
-
-- Unity/GPU rendering produces pixel noise between frames → false "changed"
-- Loading spinners and status bar clocks → false "unchanged" never reached
-- Full-frame hash includes window chrome → irrelevant churn
-
-**dhash** (difference hash) with Hamming distance ≤ 5 treats near-identical frames as stable. Combine with `region_*` to monitor only the editor canvas.
-
-## Future: evidence bundles (Phase 9)
-
-On assert failure, optionally return:
-
-```json
-{
-  "before_path": "...",
-  "after_path": "...",
-  "diff_path": "...",
-  "changed_pct": 0.3,
-  "recovery_tip": "Call automation_windows(focus) before retry."
-}
-```
-
-Host LLM reviews images; cua-mcp does not run vision models server-side.
-
-## Tests
-
-Unit tests use synthetic PIL images in `tmp_path` — no Windows GUI required for hash/diff/assert_changed/unchanged/wait_stable on static files.
-
-16 tests in `tests/test_automation_assert.py` (15 pass; `assert_text` skips if Tesseract binary not in PATH).

package/mcps/windows-computer-use-mcp/docs/CUA_PARITY.md

@@ -1,39 +0,0 @@
-# Cua-style desktop loop (operator)
-
-**Roadmap:** [CUA_PARITY_ROADMAP.md](./CUA_PARITY_ROADMAP.md)  
-**Fleet doc:** [CUA_DRIVER_AND_PYWINAUTO.md](file:///D:/Dev/repos/mcp-central-docs/patterns/CUA_DRIVER_AND_PYWINAUTO.md)
-
-## Quick loop
-
-```text
-1. automation_windows("find", title="Excel", partial=True)  → HWND
-2. get_window_state({ window_handle, capture_mode: "som" }) → snapshot_id
-3. automation_elements({ operation: "click", window_handle, snapshot_id, element_index: 3, dispatch: "background" })
-4. get_window_state(...)  → verify
-```
-
-## Excel while Cursor is focused
-
-**Intent:** Yes — that is what `dispatch=background` and per-window snapshots are for.
-
-**Reality (Phase 1):** Partial. Office UIA often accepts `invoke` / `click_input` without foreground; some controls still need `dispatch: "foreground"`. Coordinate fallback **moves the real cursor** — not true Cua no-warp yet.
-
-Use a **dedicated MCP profile** (not default IDE webapp chain). Read [SAFETY.md](./SAFETY.md).
-
-## Environment
-
-```powershell
-$env:WINDOWS_COMPUTER_USE_MCP_DISPATCH = "background"   # optional; default foreground
-```
-
-## fleet-agent-mcp
-
-With pywinauto HTTP on **10789**, fleet-agent **`fleet_bridge`** alias **`pywinauto`** can call `get_window_state` and `automation_elements`. See [fleet-agent-mcp/docs/pywinauto-cua-loop.md](file:///D:/Dev/repos/fleet-agent-mcp/docs/pywinauto-cua-loop.md).
-
-Pair **libreoffice-mcp** for headless PDF/convert; use pywinauto e2e against live Calc for GUI verification (`pytest -m e2e`).
-
-## MCP config snippet
-
-```powershell
-uv run windows-computer-use-mcp mcp-config
-```

package/mcps/windows-computer-use-mcp/docs/DEVELOPMENT.md

@@ -1,51 +0,0 @@
-# Development
-
-**Version:** `pyproject.toml` → `[project] version` (currently 0.5.x).
-
-## Quick start
-
-```powershell
-uv sync
-just install          # same as uv sync
-just start            # web_sota + API (10788 / 10789)
-just dev              # API only with reload
-```
-
-## Quality gate (matches CI)
-
-```powershell
-uv run ruff check src tests
-uv run pytest tests -q -m "not e2e and not slow"
-```
-
-With `CI=true`, hardware and destructive tests are skipped automatically — see [TESTING.md](TESTING.md).
-
-## Layout
-
-| Path | Purpose |
-|------|---------|
-| `src/windows_computer_use_mcp/` | FastMCP server, portmanteau tools, safety gates |
-| `web_sota/` | Vite operator UI + FastAPI routes |
-| `web_sota/src-tauri/` | Tauri 2 desktop shell (port **10789** backend) |
-| `mcpb/` | Claude Desktop bundle staging |
-| `tests/` | pytest (unit + optional hardware/e2e) |
-| `examples/` | Local demos (`just demo`, `just paint-demo`) |
-
-## Common recipes
-
-```powershell
-just --list
-just mcpb-pack
-just demo
-```
-
-Tauri installer: `uv sync --extra desktop`, then `npm run tauri:build` from `web_sota/` (see [DESKTOP_APP.md](DESKTOP_APP.md)).
-
-## Fleet references
-
-- **mcp-central-docs** — `standards/testing-environment-aware.md`, `patterns/WINDOWS_COMPUTER_USE_MCP_SAFETY.md`, `standards/MCPB_PACKAGING_STANDARDS.md`
-- **Sibling:** [autohotkey-mcp](https://github.com/sandraschi/autohotkey-mcp) — hotkey scriptlets, not native UIA
-
-## Historical dev notes
-
-Fleet-imported contributor dumps (notepadpp-mcp era) live under [development/archive/](development/archive/README.md) — **do not** treat as current guidance.