ops-clientlisted

# Ops Client ## Overview Operate and verify real desktop client windows. Treat platform automation as adapter-specific: the current built-in evidence path is macOS-first, while Windows and Linux require an available platform adapter before equivalent claims can be made. Use `dev-frontend` for UI code changes. ## Workflow 1. Identify the specified client target and action scope: app name, repository path, package/app directory, process, PID, visible window, platform, requested evidence, and whether observation, capture, launch, restart, focus, or a named semantic interaction is explicitly authorized. 2. Run a capability preflight and record available/unavailable/unknown for: - process enumeration and runtime-source inspection; - window enumeration with stable window identifiers; - window-specific screenshot capture; - Accessibility/control-tree inspection and semantic actions; - background-safe operation without stealing mouse/focus; - app launch/restart and permission state. 3. If working from a repository, confirm whether it contains a desktop/client app by checking manifests and source layout such as `src-tauri/`, `tauri.conf.*`, Electron configs, native targets, package scripts, justfile tasks, or README run instructions. 4. Confirm the startup command and runtime source before verification: dev command, debug bundle, release app, Electron/native run command, or `Not found`/`Not verified` when unclear. 5. Select the platform adapter: - **macOS:** i