capture-release-evidences-cx

# Capture Release Evidences Workflow Use this workflow to automatically drive a browser-automation agent to explore the newly deployed or locally running application and record evidence of the UI changes introduced in the latest release. > **Tool mapping note (v3.8):** The `browser_subagent` tool referenced below is specific to an earlier agent runtime. In Claude Code, substitute with the available browser MCP tools (e.g. `mcp__claude-in-chrome__*`) for navigation/screenshots, plus the `Write` tool for saving artifacts. The high-level steps remain the same regardless of the browser-automation surface in use. ## Prerequisites - OmniRoute must be actively running and accessible (e.g. locally at `http://localhost:20128` or on the Local VPS at `http://192.168.0.15:20128`). - The user must provide the target URL to be tested, or default to `http://192.168.0.15:20128`. ## Workflow Steps ### 1. Identify Target Features Review the `CHANGELOG.md` for the latest version to map out the new UI elements. For example: - **CLI Tools Settings** - **New Provider/Model Listings (e.g., Gemini 3.1, Qoder PAT)** - **New Feature Modals** ### 2. Run the Browser Subagent For each identified feature, invoke the `browser_subagent` using the `default_api:browser_subagent` tool. **Important Task Guidelines for the Subagent:** - `TaskName`: Give it a clear name like "Validate CLIProxyAPI Tool Tab". - `TaskSummary`: "Navigate to the CLI Tools tab and verify the new Integration settings." - `Tas...