Migrate from Playwright

npm install -g testerarmy
ta auth

Migrate this repository's Playwright test suite to TesterArmy using the
TesterArmy CLI (`ta`). Verify auth first with `ta status --json`, and use
`ta --help` plus subcommand help to discover commands. Prefer --json output.

1. Discover: find playwright.config.* and all spec files (*.spec.ts,
   *.spec.js, *.test.ts under the configured testDir). Read the config to
   determine the baseURL and any storageState/auth setup projects.

2. Create a TesterArmy project (skip if one exists in `ta projects list`):
   echo '{"name":"<repo name>","url":"<baseURL>","projectType":"web"}' | ta projects create --json

3. Save durable context as project memories (category site_structure,
   importance high): key routes, the login URL, anything from global-setup
   files that future test runs should know.
   echo '{"category":"site_structure","title":"...","content":"...","importance":"high"}' | ta memories create --project <projectId> --json

4. Convert each Playwright test() into a TesterArmy test:
   - Express the USER INTENT of each action in plain English. Drop all
     selectors, locators, waitFor calls, and retries - the TesterArmy agent
     finds elements visually and waits on its own.
   - page.goto/click/fill/selectOption -> steps with type "act"
   - expect(...) assertions -> steps with type "assert"
   - login fixtures or storageState setup -> one step with type "login"
   - Keep tests focused: 3-10 steps. Split test() bodies that cover
     multiple flows into separate tests.
   - Skip API-only tests, component tests, and page.route() mocking logic.
   Create each test:
   echo '{"title":"<test name>","description":"Migrated from <spec file>","steps":[{"title":"Navigate to /login","type":"act"},{"title":"Dashboard loads","type":"assert"}]}' | ta tests create --project <projectId> --json
   Step types: act, assert, login, files, screenshot, javascript, microphone.

5. Never hardcode passwords in test steps. If specs use env vars or
   storageState for auth, tell me which credentials to add and I will run:
   echo '{"kind":"login","label":"...","username":"...","password":"..."}' | ta projects credentials-create <projectId> --json

6. Verify: save a cloud-reachable preview or tunnel URL with
   ta projects environments-create <projectId> --name Verification --url <url> --json
   Then run each migrated test in TesterArmy cloud with
   `ta tests run <testId> --env verification --wait --json` and report results.
   Exit code 0 = pass, 1 = fail.

7. Report a summary table: spec file -> TesterArmy test ID -> run result,
   plus a list of anything you intentionally skipped and why.