e2e

Run end-to-end tests via the CI workflow. The user may pass `$ARGUMENTS` to filter to a specific test case by name (e.g., `hello-world`, `phone-setup`). If not provided, infer options from context (see below). ## Steps ### 1. Determine options **Experimental tests:** Always include `--experimental` by default. The user can pass `--no-experimental` to exclude them. **Branch detection:** Check what branch you're on via `git branch --show-current`. If you're on a branch other than `main`, automatically pass `-b <branch-name>` so the CI run tests against that branch. The user can override with `-b <other-branch>` explicitly. **Test case filter:** Determine which test case to target: 1. If the user passes a bare word argument (e.g., `phone-setup`), use that as the filter. 2. Otherwise, look at the conversational context - if you've been working on or discussing a specific e2e test case (e.g., editing `playwright/cases/phone-setup.md`), automatically target that test case. 3. If neither applies, run all tests. **Additional flags from `$ARGUMENTS`:** - `--xcode` uses the agent-xcode (AXUIElement) runner - `-d` or `--detach` triggers the run and exits without polling - `--no-experimental` overrides the default and excludes experimental tests ### 2. Trigger the CI run ```bash cd playwright && bun run scripts/agent-ci.ts <options> ``` Map the resolved options: - Test case filter: `-t <case-name>` - Experimental (default on): `--experimental` - Branch: `-b <branch-name>` - Xco...