What problem does it solve? Product acceptance for aohys.com requires proving that real user journeys actually work in the browser, not just that static checks pass. This Skill provides a controlled, evidence-backed verification workflow that drives the public Astro site and private dashboard with Computer Use while keeping production strictly read-only. ## Core Features & Use Cases - Deterministic readiness probes: The doctor command validates origin reachability per app and environment before any browser session starts, confining local runs to declared loopback origins and production to read-only checks. - Plan-bound Computer Use execution: The orchestrator creates a versioned, SHA-256-bound execution plan that a neutral executor follows exactly, while a separate vision-capable judge owns the PASS, FAIL, BLOCKED, or INCONCLUSIVE verdict. - Private evidence records: Screenshots, console and network observations, and before/after probe results persist under a private verification directory, so authenticated dashboard journeys are only marked proven with real run evidence. - Use Case: After changing the dashboard Leads page, run the changed-scope feature map selection, launch the dashboard, execute the authorized Leads observation journey with Computer Use, and record a verified verdict tied to the exact candidate tree. ## Quick Start Verify the public site by asking the agent to run the product doctor for the site app locally and then execute the mapped home page journey with Computer Use.
