cherry-pr-test

# Cherry Studio PR Test Use this workflow for a bounded PR test. Use `cherry-electron-dev` for ongoing implementation or debugging in the current checkout. ## Prerequisites and safety - Require authenticated `gh`, `pnpm`, and installed project dependencies. - Use Playwright/CDP or optional `agent-browser` for UI control. - Before touching Electron, read [Electron Instance Management](../cherry-electron-dev/references/electron-instance.md) and select its `ephemeral` policy. - Treat that reference as the only authority for discovery, target selection, launch, replacement, shutdown, tracking, and troubleshooting. - Never discard local changes. Stop and ask if checkout would overwrite them. - Show the report before posting it anywhere. `$ARGUMENTS` may contain a PR number, PR URL, `latest`/`recent`, or nothing. ## Workflow ### 1. Resolve and inspect the PR If no PR is specified, list recent PRs and ask the user to choose unless they requested the latest: ```bash gh pr list --repo CherryHQ/cherry-studio --state open --limit 10 \ --json number,title,author,createdAt,headRefName,changedFiles ``` Record the current branch for restoration, inspect the PR, then check it out: ```bash git status --short git branch --show-current gh pr view <NUMBER> --json title,body,author,headRefName,files gh pr checkout <NUMBER> ``` Read the changed files and nearby instructions. Record the exact checked-out HEAD. ### 2. Analyze and start the app Run static analysis while the app s...