cherry-regression-test

# Cherry Regression Test Run deterministic Playwright E2E tests against one driver-owned Cherry Studio process per platform. The tested product includes Chat, Agents, MCP, Skills, knowledge bases, translation, image generation, and code tools; an LLM test agent does not control the test run. ## CI contract Use `.github/workflows/e2e-regression-test.yml` as the entry point. It: 1. Resolves a trusted branch or release tag. 2. Initializes an isolated directory under the GitHub runner temporary folder. 3. Installs the application and the code tools under test. 4. Launches one owned Electron process with CDP enabled. 5. Runs the ten files in `tests/e2e/regression/` from simple to complex. 6. Continues after a failed phase so later results are still collected. 7. Produces English platform and aggregate reports, then enforces the verdict. 8. Stops only the Electron process recorded in the isolated run directory. Do not add an LLM tool loop, MCP control server, turn limit, or a second Electron launch for each test. A restart is allowed only where the case contract explicitly verifies persistence or switches from the clean startup profile to the authenticated shared profile. ## Configuration The workflow reads these repository variables and secrets: - `CHERRY_TEST_CUSTOM_PROVIDER_BASE_URL` - `CHERRY_TEST_CUSTOM_PROVIDER_ANTHROPIC_BASE_URL` - `CHERRY_TEST_CUSTOM_PROVIDER_API_KEY` - `CHERRY_TEST_CUSTOM_PROVIDER_CHAT_MODEL` - `CHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_BASE_URL` - `CH...