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; - screen-session state as `unlocked`, `locked`, or `unknown`, with the evidence source. 3. Apply the screen-session gate before any window operation. When locked, do not unlock or wake the display, focus or activate a window, send keyboard input, move the pointer, or click through pointer/coordinate automation. Permit window-level capture or inspection only when the selected adapter directly proves that exact action is background-safe and does not require those effects