test(expo): upgrade e2e to 0.22.0

.changeset/quiet-tests-climb.md

@@ -0,0 +1,2 @@
+---
+---

.claude/skills/verify-clerk-expo/SKILL.md

@@ -168,7 +168,7 @@ The specs under `specs/features/<feature>/` are committed and cover the feature
 4. Fix the locators from that output until the spec passes.
 5. When the change adds or changes what `@clerk/expo` does, move the spec to `specs/features/<feature>/`, change its import to `'../../fixtures.ts'`, `git add` it, and update the feature's page and its line in `features/README.md`. A change to wording or appearance alone does not earn a committed spec, because a spec that pins a label fails on the next change of wording: leave that spec in `specs/explored/`. The run directory keeps a copy of every spec the run used.
 
-A failing spec prints `FAIL`, the first assertion message, and the path of its failure page, and `run` exits 1. The failure page (`.verify/runs/<run-id>/e2e/failures/*.md`) lists every step, the screen tree at the failure, and a screenshot. A run in which no test executed, such as a `--grep` that matches nothing, fails with `NO_SPECS` and exits 3, because it proved nothing. A run in which every selected spec is limited to the other platform is the one exception. It exits 0, prints `skip` for each spec, and its `next` line says `nothing ran: every selected spec was left out by platform, so the run proves nothing to post`. Read that line, because the exit code alone looks like a pass.
+A failing spec prints `FAIL`, the first assertion message, and the path of its failure page, and `run` exits 1. The failure page (`.verify/runs/<run-id>/e2e/results/<test>/trace.md`) lists every step, the screen tree at the failure, and a screenshot. A run in which no test executed, such as a `--grep` that matches nothing, fails with `NO_SPECS` and exits 3, because it proved nothing. A run in which every selected spec is limited to the other platform is the one exception. It exits 0, prints `skip` for each spec, and its `next` line says `nothing ran: every selected spec was left out by platform, so the run proves nothing to post`. Read that line, because the exit code alone looks like a pass.
 
 Right after `up` the CLI has not launched the test app, and `screen` opens it without the verify inputs that `host.launch` passes, so the screen is not one a spec sees. To look at a real screen, first run a spec that launches the app and taps to it. When a node may be missing, assert `await expect(locator).toBeVisible()` before you tap it. That failure reads `observed: no node (match count 0)`, and a failed tap says only `LOCATOR_NOT_FOUND`.
 

.github/workflows/verify-e2e.yml

@@ -231,8 +231,7 @@ jobs:
             ${{ env.PACKAGE }}/.verify/runs/*/e2e*/report.json
             ${{ env.PACKAGE }}/.verify/runs/*/e2e*/junit.xml
             ${{ env.PACKAGE }}/.verify/runs/*/e2e*/summary.md
-            ${{ env.PACKAGE }}/.verify/runs/*/e2e*/failures
-            ${{ env.PACKAGE }}/.verify/runs/*/e2e*/artifacts
+            ${{ env.PACKAGE }}/.verify/runs/*/e2e*/results
           retention-days: 3
           if-no-files-found: warn