The playwright install runs as the regular user, so the test must
also run without sudo to find the cached browser binaries. Port 5401
does not require root privileges.

Made-with: Cursor

- smoke: check for 'Howdy' text instead of #wpadminbar visibility
  (admin bar element exists but is CSS-hidden before JS initializes)
- ui: use getByRole('heading', { name: 'Backup' }) to avoid strict
  mode violation from 6 elements matching getByText('Backup')
- blueprints: remove blueprint-url data URL test that fails on fresh
  CI browsers (no existing OPFS site for the query param path)
- Use type-only re-export for Page in playground-fixtures
- Use proper Playwright type for goto options parameter
- Scope address bar selector to the toolbar header
- Use toBeVisible() instead of not.toBeEmpty() in waitForNestedIframes

Made-with: Cursor

…n checks

'Start over' and 'Recovery' also match multiple elements (heading +
paragraph). Use getByRole('heading') consistently for all menu sections.

Made-with: Cursor

…er timeout

Firefox and WebKit use Asyncify (not JSPI), where the WordPress body
inside the iframe may be CSS-hidden during boot. toBeVisible() fails
in this state while not.toBeEmpty() (used by core playground-website)
succeeds. Additionally, personal-wp boots are heavier (OPFS site
creation + default blueprint fetches a plugin from GitHub), so the
timeout is increased to 180s to accommodate slower Asyncify mode.

Made-with: Cursor

Firefox and WebKit fail because the WASM PHP runtime needs
SharedArrayBuffer, which requires cross-origin isolation headers
(COEP/COOP). These are provided by the service worker after it
claims the page, but on a fresh Vite dev server load the service
worker isn't active yet and the runtime never boots.

The core playground-website E2E tests already cover Firefox/WebKit
via a built app served with proper headers. Personal-wp E2E tests
focus on the UI layer and run on Chromium (with JSPI) only.

Made-with: Cursor

… ones

Blueprint execution (base64, JSON, writeFile, login, wp-cli) is
thoroughly covered by the core playground-website E2E tests. The
welcome page test already proves blueprints work through personal-wp.

Similarly, WordPress boot, auto-login, and viewport rendering are
implicitly tested by core.

Remaining 8 tests focus on what personal-wp uniquely adds:
- Default my-wordpress blueprint flow (welcome page landing)
- Personal-wp toolbar
- Address bar, Site Tools panel, menu overlay, page title, navigation

Made-with: Cursor

personal-wp forks resolve-blueprint-from-url.ts and boot-site-client.ts
from core. Add a smoke test that exercises this forked parsing → boot
chain, while avoiding re-testing shared step execution from
@wp-playground/blueprints.

Made-with: Cursor

The wordpress FrameLocator was defined in three places — the fixture,
the page object's wordpress() method, and waitForNestedIframes(). Now
wordpress() is the single source of truth and both callers delegate to it.

Made-with: Cursor

…orNestedIframes()

Both methods always operate on this.page — the parameter was never
called with a non-default value.

Made-with: Cursor