Build deployed Playwright data-flow E2E coverage

[BASIC-BIT]

Current state

• Playwright exists under apps/web/e2e.
• Current tests are public-route smoke and visual coverage using deterministic fixtures.
• They assert pages render and capture screenshots for /, /discover, /submit, /server-status, /deployment, public profile pages, world pages, and event pages.
• They do not yet exercise signed-in flows, mutations, claim flows, email verification, adapter verification, or deployed Convex data movement.

Goal

Build an E2E harness that clicks through the important product flows and asserts both UI state and backend data state.

Recommended environment model

• Keep local Convex Playwright for fast deterministic smoke and regression tests.
• Add a deployed development/staging Convex target for integration E2E against real hosted services.
• Keep production read-only for smoke checks only.
• Prefer a dedicated seeded E2E namespace/test account model so tests can create/delete their own data without touching real users.
• For PR previews, either wire Vercel preview to a disposable Convex preview deployment or explicitly run only route smoke until preview backend isolation is available.

Candidate flow coverage

• Account page signed-out and sign-in-required states.
• Email/password signup, SES verification code path, and post-verification account readiness.
• Profile submission creates an unclaimed person/community record and the public page/search reflects it.
• Field visibility changes affect direct profile pages versus discovery/search surfaces.
• Discord person claim path grants claimed_unverified owner control.
• Discord community admin claim creates a pending request and adapter verification grants verified ownership when mocked or test-guild-backed evidence passes.
• VRChat/VRCLinking proof flow creates a proof code, test adapter returns verified/not verified, and ownership state updates correctly.
• Search/discovery flow shows only published, public-surfacing, visibility-allowed fields.
• Event/world/profile cross-link flows preserve public projections after mutations.

Acceptance criteria

• pnpm test:e2e has at least one mutation-backed user journey, not only public render checks.
• CI separates public preview smoke from mutation-backed deployed integration tests.
• Test data is isolated by run ID and cleaned up or marked disposable.
• Tests can run against local Convex and against an explicitly selected deployed dev/staging Convex URL.
• Docs explain when to use local, preview, dev/staging, and production smoke modes.

Notes

This should be split before implementation if it becomes too large. The first useful slice is a signed-out/sign-in-required/public-submission smoke plus one authenticated profile submission against a seeded dev deployment.

[BASIC-BIT]

Completed the deployed Playwright data-flow E2E scope.

Delivered:

• Local mutation-backed E2E coverage for profile submission, field visibility, auth/email verification, Discord claim, community admin claim, and VRChat/VRCLinking proof flows.
• Hosted staging mutation health against https://staging.vrdex.net.
• Hosted optional flags enabled and green:
  • VRDEX_HOSTED_E2E_EXTENDED_PROFILE_FLOW=true
  • VRDEX_HOSTED_E2E_AUTH_HELPERS=true
  • VRDEX_HOSTED_E2E_ADAPTER_HELPERS=true
• Staging Vercel deployment is live and aliased to staging.vrdex.net.
• Provider-side hosted E2E env state is documented in deployment docs.

Relevant PRs:

• Add auth claim E2E flow #109
• Bundle E2E coverage gates #110
• Scope hosted discovery visibility assertions #111
• Shorten hosted adapter E2E alias #112
• Document hosted E2E rollout envs #113

Validation:

• Hosted Data Flow Health run 26743846965 passed with extended profile, auth helpers, and adapter helpers enabled.

Remaining credential-gated IaC/deploy-token work has been split to #114, so this E2E coverage issue can close.