# Connect surface E2E — request

**Status: BLOCKED on infrastructure — do not launch yet.** Headless browsers are refused on the
workstation (`install-headless-guard`, `mode=blocking identity=workstation`, exit 97), and the only
permitted WordPress target is the Podman instance on `http://localhost:8080`, which a browser
running on a buildbox cannot reach. `e2e-remote` offers no reverse tunnel. Unblock by giving the
remote browser a route to that WordPress; then run this request.

**Goal:** E2E coverage for the connect surface, green against the local WordPress.

**Files:** `tests/e2e/connect-onboarding.spec.js` (exists, unverified), `tests/e2e/admin-snappy-all-pages.spec.js` (modify).

`connect-onboarding.spec.js` mocks the connect REST surface and needs no backend. Get it green,
fixing what it catches in the plugin — never by weakening the spec.

`admin-snappy-all-pages.spec.js` collects admin routes and asserts each renders within the snappy
budget. Two gaps:
- The `fields` route entry near line 121 does not match the route the admin registers, which stops
  collection before the rest of the list. Fix the entry to the real route.
- The connect routes (onboarding, account) are not covered. Add them to the collected route list.

**Acceptance:**
- Run from `tests/e2e/`: `npx playwright test connect-onboarding.spec.js --project=chromium` — all pass.
- Run from `tests/e2e/`: `npx playwright test admin-snappy-all-pages.spec.js --project=chromium` — all
  pass, and the run reports the onboarding and account routes among those checked.

**Test target constraint (absolute):** the ONLY permitted WordPress target is the local Podman
instance at `http://localhost:8080`. `dev3.press.zone` is a separate production instance and `dev1`
is a production host — never point a test, smoke, or screenshot at either.