wordpress-agent-kit 0.3.2 → 0.5.1

package/.agents/skills/wp-wpengine/scripts/ci-gate.sh

@@ -0,0 +1,118 @@
+#!/usr/bin/env bash
+# ci-gate.sh — run the full CI gate locally before pushing.
+#
+# Mirrors what GitHub Actions ci-gate.yml runs. Use this before any push
+# to a branch that triggers a WP Engine deploy.
+#
+# Usage:
+#   bash scripts/ci-gate.sh              # run both gates
+#   bash scripts/ci-gate.sh --php-only   # PHP gate only
+#   bash scripts/ci-gate.sh --js-only    # JS/TS gate only
+#
+# Exit code: 0 = all passed, 1 = at least one check failed.
+
+set -uo pipefail
+root="$(git rev-parse --show-toplevel)"
+cd "$root"
+
+PHP_ONLY=false
+JS_ONLY=false
+for arg in "$@"; do
+  [[ "$arg" == "--php-only" ]] && PHP_ONLY=true
+  [[ "$arg" == "--js-only" ]] && JS_ONLY=true
+done
+
+PASS=0
+FAIL=0
+
+run() {
+  local label="$1"; shift
+  echo "▶ $label"
+  if "$@" 2>&1; then
+    echo "  ✓ $label"
+    ((PASS++))
+  else
+    echo "  ✗ FAILED: $label"
+    ((FAIL++))
+    return 1
+  fi
+}
+
+# ── PHP gate ──────────────────────────────────────────────────────────────────
+if ! $JS_ONLY; then
+  echo ""
+  echo "── PHP gate ──────────────────────────────────────────────────────────"
+  if command -v composer >/dev/null 2>&1 && [ -f composer.json ]; then
+    if [ ! -d vendor ]; then
+      echo "▶ composer install"
+      composer install --no-interaction --quiet
+    fi
+
+    run "php -l (all tracked PHP files)" \
+      bash -c 'git ls-files "*.php" | xargs -P4 php -l > /dev/null'
+
+    if [ -x vendor/bin/phpcs ]; then
+      run "phpcs (WordPress coding standards)" composer run phpcs
+    else
+      echo "  ⚠  phpcs not found — run: composer install"
+    fi
+
+    if [ -x vendor/bin/phpstan ]; then
+      run "phpstan (static analysis)" composer run phpstan
+    else
+      echo "  ⚠  phpstan not found — run: composer install"
+    fi
+  else
+    echo "  ⚠  composer not available or no composer.json — skipping PHP gate"
+  fi
+fi
+
+# ── JS/TS gate ────────────────────────────────────────────────────────────────
+if ! $PHP_ONLY; then
+  echo ""
+  echo "── JS/TS gate ────────────────────────────────────────────────────────"
+  if [ -f package.json ]; then
+    if [ ! -d node_modules ]; then
+      echo "▶ npm install"
+      npm install --silent
+    fi
+
+    if [ -x node_modules/.bin/biome ]; then
+      run "biome check (lint + format)" npx biome check .
+    else
+      echo "  ⚠  biome not installed — run: npm install"
+    fi
+
+    if npm run typecheck --if-present 2>/dev/null; then
+      ((PASS++))
+    elif command -v tsc >/dev/null 2>&1 || [ -x node_modules/.bin/tsc ]; then
+      run "tsc --noEmit (type check)" npx tsc --noEmit
+    fi
+
+    if npm run test --if-present 2>/dev/null; then
+      ((PASS++))
+    fi
+
+    if npm run build --if-present 2>/dev/null; then
+      ((PASS++))
+    fi
+  else
+    echo "  ⚠  No package.json — skipping JS/TS gate"
+  fi
+fi
+
+# ── Summary ───────────────────────────────────────────────────────────────────
+echo ""
+echo "── CI Gate Result ────────────────────────────────────────────────────"
+echo "  Passed : $PASS"
+echo "  Failed : $FAIL"
+echo ""
+
+if [[ "$FAIL" -eq 0 ]]; then
+  echo "✅ Gate green — safe to push."
+  exit 0
+else
+  echo "❌ Gate failed — fix the issues above before pushing."
+  echo "   --no-verify is not a valid workaround; CI will catch the same failures."
+  exit 1
+fi

package/.agents/skills/wp-wpengine/scripts/wpe-check.sh

@@ -0,0 +1,89 @@
+#!/usr/bin/env bash
+# wpe-check.sh — verify SSH connectivity to all configured WP Engine environments.
+#
+# Reads installs from wp-cli.yml @aliases (ssh: field) or from WPE_INSTALLS env var.
+# Useful after first-time machine setup or when debugging SSH issues.
+#
+# Usage:
+#   bash scripts/wpe-check.sh
+#   WPE_INSTALLS="mysite mysitestg mysitedev" bash scripts/wpe-check.sh
+#
+# Exit code: 0 = all connected, 1 = at least one failed.
+
+set -uo pipefail
+root="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
+cd "$root"
+
+SSH_OPTS="-o BatchMode=yes -o ConnectTimeout=8 -o StrictHostKeyChecking=accept-new"
+
+# ── Discover installs from wp-cli.yml @aliases ────────────────────────────────
+declare -A ALIAS_MAP   # install → alias label
+CURRENT_ALIAS=""
+
+if [ -f wp-cli.yml ]; then
+  while IFS= read -r line; do
+    if [[ "$line" =~ ^@([a-zA-Z0-9_-]+): ]]; then
+      CURRENT_ALIAS="${BASH_REMATCH[1]}"
+    elif [[ "$line" =~ ^[[:space:]]+ssh:[[:space:]]+([^@[:space:]]+)@[^[:space:]]+ && -n "$CURRENT_ALIAS" ]]; then
+      INSTALL="${BASH_REMATCH[1]}"
+      ALIAS_MAP["$INSTALL"]="@${CURRENT_ALIAS}"
+      CURRENT_ALIAS=""
+    fi
+  done < wp-cli.yml
+fi
+
+# Fallback: WPE_INSTALLS env var
+if [ "${#ALIAS_MAP[@]}" -eq 0 ] && [ -n "${WPE_INSTALLS:-}" ]; then
+  for slug in $WPE_INSTALLS; do
+    ALIAS_MAP["$slug"]="$slug"
+  done
+fi
+
+if [ "${#ALIAS_MAP[@]}" -eq 0 ]; then
+  echo "No WP Engine installs found."
+  echo ""
+  echo "Options:"
+  echo "  1. Add @aliases with 'ssh: <install>@<install>.ssh.wpengine.net' to wp-cli.yml"
+  echo "  2. Set WPE_INSTALLS='slug1 slug2 slug3' environment variable"
+  exit 1
+fi
+
+echo ""
+echo "── WP Engine SSH connectivity ────────────────────────────────────────"
+printf "  %-25s %-15s %-12s %s\n" "Install" "Alias" "Status" "WP version"
+echo "  ─────────────────────────────────────────────────────────────────"
+
+PASS=0
+FAIL=0
+
+for INSTALL in "${!ALIAS_MAP[@]}"; do
+  ALIAS="${ALIAS_MAP[$INSTALL]}"
+  SSH_HOST="${INSTALL}.ssh.wpengine.net"
+
+  WP_VERSION=$(ssh $SSH_OPTS "${INSTALL}@${SSH_HOST}" \
+    wp core version --skip-plugins --skip-themes 2>/dev/null || echo "")
+
+  if [ -n "$WP_VERSION" ]; then
+    printf "  %-25s %-15s %-12s %s\n" "$INSTALL" "$ALIAS" "✓ connected" "$WP_VERSION"
+    ((PASS++))
+  else
+    printf "  %-25s %-15s %-12s %s\n" "$INSTALL" "$ALIAS" "✗ FAILED" "—"
+    ((FAIL++))
+  fi
+done
+
+echo ""
+echo "  $PASS connected  |  $FAIL failed"
+
+if [[ "$FAIL" -gt 0 ]]; then
+  echo ""
+  echo "Troubleshooting:"
+  echo "  • Confirm key exists:  ls -la ~/.ssh/wpengine_ed25519"
+  echo "  • Confirm permissions: chmod 600 ~/.ssh/wpengine_ed25519"
+  echo "  • Trust the host:      ssh-keyscan -H ssh.wpengine.net >> ~/.ssh/known_hosts"
+  echo "  • Check portal:        https://my.wpengine.com/ssh_keys"
+  echo "  • Verify git access:   ssh git@git.wpengine.com info"
+fi
+
+echo ""
+[[ "$FAIL" -eq 0 ]] && exit 0 || exit 1

package/.agents/skills/wp-wpengine/scripts/wpe-preflight.sh

@@ -0,0 +1,104 @@
+#!/usr/bin/env bash
+# wpe-preflight.sh — pre-deploy sanity checks for a WP Engine environment.
+#
+# Verifies SSH access, WP-CLI, site URL consistency, HTTP health, and
+# active plugin count before any deploy touches production or staging.
+#
+# Usage:
+#   INSTALL=mysite bash scripts/wpe-preflight.sh [staging|production]
+#   WPE_INSTALL=mysite bash scripts/wpe-preflight.sh production
+#
+# Exit code: 0 = all checks passed (safe to deploy), 1 = at least one failed.
+
+set -uo pipefail
+
+ENV="${1:-production}"
+INSTALL="${WPE_INSTALL:-${INSTALL:-}}"
+
+if [ -z "$INSTALL" ]; then
+  echo "❌ Usage: INSTALL=<slug> bash scripts/wpe-preflight.sh [staging|production]"
+  echo "   The install slug is the WP Engine environment name (e.g., 'mysite', 'mysitestg')."
+  exit 1
+fi
+
+SSH_HOST="${INSTALL}.ssh.wpengine.net"
+SSH_OPTS="-o BatchMode=yes -o ConnectTimeout=15 -o StrictHostKeyChecking=accept-new"
+WP="ssh $SSH_OPTS ${INSTALL}@${SSH_HOST} wp"
+
+PASS=0
+FAIL=0
+
+check() {
+  local label="$1"; shift
+  printf "  %-50s" "$label"
+  local output
+  if output=$("$@" 2>&1); then
+    echo "✓  $output"
+    ((PASS++))
+  else
+    echo "✗  FAILED"
+    echo "     $output" >&2
+    ((FAIL++))
+  fi
+}
+
+echo ""
+echo "── WP Engine preflight: ${INSTALL} (${ENV}) ─────────────────────"
+echo ""
+
+# ── SSH ───────────────────────────────────────────────────────────────────────
+echo "SSH"
+check "SSH gateway reachable" \
+  ssh $SSH_OPTS "${INSTALL}@${SSH_HOST}" echo "connected"
+
+check "WP-CLI available" \
+  $WP --info --skip-plugins --skip-themes
+
+# ── WordPress ─────────────────────────────────────────────────────────────────
+echo ""
+echo "WordPress"
+check "WP core version" \
+  $WP core version --skip-plugins --skip-themes
+
+check "siteurl option readable" \
+  $WP option get siteurl --skip-plugins --skip-themes
+
+check "Active plugins present (count > 0)" \
+  bash -c "COUNT=\$(${WP} plugin list --status=active --format=count --skip-plugins --skip-themes 2>&1); echo \"\$COUNT active\"; [[ \"\$COUNT\" -gt 0 ]]"
+
+check "No pending DB upgrades" \
+  $WP core update-db --dry-run --skip-plugins --skip-themes
+
+# ── HTTP health ───────────────────────────────────────────────────────────────
+echo ""
+echo "HTTP health"
+SITE_URL=$(ssh $SSH_OPTS "${INSTALL}@${SSH_HOST}" \
+  wp option get home --skip-plugins --skip-themes 2>/dev/null || echo "")
+
+if [ -n "$SITE_URL" ]; then
+  check "Homepage returns 2xx/3xx" \
+    bash -c "STATUS=\$(curl -s -o /dev/null -w '%{http_code}' -L --max-time 15 '${SITE_URL}'); echo \"HTTP \$STATUS\"; [[ \"\$STATUS\" -ge 200 && \"\$STATUS\" -lt 400 ]]"
+
+  check "No PHP errors in homepage body" \
+    bash -c "BODY=\$(curl -sL --max-time 15 '${SITE_URL}'); echo \"\${#BODY} chars\"; ! echo \"\$BODY\" | grep -qi 'fatal error\|parse error\|warning: '"
+
+  check "wp-json REST API responds" \
+    bash -c "STATUS=\$(curl -s -o /dev/null -w '%{http_code}' --max-time 10 '${SITE_URL}/wp-json/wp/v2/'); echo \"HTTP \$STATUS\"; [[ \"\$STATUS\" -ge 200 && \"\$STATUS\" -lt 400 ]]"
+else
+  echo "  ⚠  Could not retrieve site URL — skipping HTTP checks"
+fi
+
+# ── Result ────────────────────────────────────────────────────────────────────
+echo ""
+echo "── Preflight result ──────────────────────────────────────────────────"
+echo "  Passed : $PASS"
+echo "  Failed : $FAIL"
+echo ""
+
+if [[ "$FAIL" -eq 0 ]]; then
+  echo "✅ All checks passed — safe to deploy to ${ENV}."
+  exit 0
+else
+  echo "❌ Preflight failed — resolve the issues above before deploying to ${ENV}."
+  exit 1
+fi

package/.agents/skills/wpds/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: wpds
+description: "Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc."
+license: GPL-2.0-or-later
+compatibility: "Requires WPDS MCP server configured and running. Targets WordPress 6.9+ (PHP 7.2.24+)."
+---
+
+# WordPress Design System (WPDS)
+
+## Prerequisites
+
+This skill works best with the **WPDS MCP server** installed. The MCP provides access to WordPress Design System documentation and resources, such as components and DS token lists.
+
+The following terms should be treated as synonyms:
+- "WordPress" and "WP";
+- "Design System" and "DS";
+- "WordPress Design System" and "WPDS".
+
+## When to use
+
+Use this skill when the user mentions:
+
+- building and/or reviewing any UI in a WordPress-related context (for example, Gutenberg, WooCommerce, WordPress.com, Jetpack, etc etc);
+- WordPress Design System, WPDS, Design System;
+- UI components, Design tokens, color primitives, spacing scales, typography variables and presets;
+- Specific component packages such as @wordpress/components or @wordpress/ui;
+
+## Rules
+
+### Use the WPDS MCP server to access WPDS-related documentation
+
+- Use the WPDS MCP server to retrieve the canonical, authoritative documentation:
+  - reference site (`wpds://pages`)
+  - list of available components (`wpds://components`) and specific component information (`wpds://components/:name`)
+  - list of available tokens (`wpds://design-tokens`)
+- DO NOT search the web for canonical documentation about the WordPress Design System. If asked by the user, push back and ask for confirmation, warning them that the MCP server is the best place to provide information
+
+### Required documentation
+
+Before working on any WPDS-related tasks, make sure you read relevant documentation on the reference site. This documentation should take the absolute precedence when evaluating the best course of action for any given tasks.
+
+### Boundaries
+
+- Skip non-UI related aspects of an answer (for example, fetching data from stores, or localizing strings of text).
+- Focus on building UI that adheres as much as possible to the WPDS best practices, uses the most fitting WPDS components/tokens/patterns.
+
+### Tech stack
+
+- Unless you are told otherwise (or gathered specific information from the local context of the request), assume the following tech stack: TypeScript, React, CSS.
+
+### Validation
+
+- If the local context in which a task is running provide lint scripts, use them to validate the proposed code output when possible.
+
+## Output
+
+- As a recap at the end of your response, provide a clear and concise explanation of what the solution does, and add context to why each decision was made.
+- Be explicit about the boundaries, ie. what was explicitly left out of the task because not relevant (eg non-ui related).
+- Provide working code snippets

package/.github/agents/wp-architect.agent.md

@@ -14,8 +14,7 @@ When a task is assigned, you must retrieve information in this sequence:
 
 1.  **Local Project Instructions**: Read `.github/instructions/wordpress-workflow.instructions.md` to understand the specific prefix, folder structure, and dev workflow for this repo.
 
-2.  **Agent Skills**: Consult the `.github/skills/` directory.
-
+2.  **Agent Skills**: Consult the `.agents/skills/` directory.
     - Reference `wp-project-triage` to confirm if you are in a Plugin or Theme context.
     - Reference `wp-block-development` for any Gutenberg/React tasks.
     - Reference `wp-playground` to provide testable blueprints for your code.

package/.github/copilot-instructions.md

@@ -1,2 +1,2 @@
 @workspace /AGENTS.md
-@workspace / .github/instructions/wordpress-workflow.instructions.md
+@workspace / .github/instructions/wordpress-workflow.instructions.md

package/.github/instructions/wordpress-workflow.instructions.md

@@ -1,10 +1,10 @@
 \# WordPress Agent Skills Workflow
 
-This repo uses a local, filesystem-based set of WordPress agent skills under `.github/skills/`. Follow these procedures for every interaction.
+This repo uses a local, filesystem-based set of WordPress agent skills under `.agents/skills/`. Follow these procedures for every interaction.
 
 \## 1. Skill Discovery & Activation
 
-\- \*\*Always start by scanning \`.github/skills/\`\*\* to see which specialized modules are active.
+\- \*\*Always start by scanning \`.agents/skills/\`\*\* to see which specialized modules are active.
 
 \- If the user asks for a Block, explicitly activate the \`wp-block-development\` skill.
 
@@ -38,4 +38,4 @@ Before finalizing a response:
 
 2\. Check if a [WordPress.org Plugin Handbook]\(https://developer.wordpress.org) rule supersedes a generic community pattern.
 
-3\. State which skill was used (e.g., \*"Applied patterns from wp-block-development"\*).
+3\. State which skill was used (e.g., \*"Applied patterns from wp-block-development"\*).

package/.github/skills/wp-playground/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wp-playground
-description: "Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug)."
+description: "Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, PHPUnit testing, E2E Playwright testing, programmatic runCLI API, and debugging (Xdebug)."
 license: GPL-2.0-or-later
 compatibility: "Targets WordPress 6.9+ (PHP 7.2.24+). Playground CLI requires Node.js 20.18+; runs WP in WebAssembly with SQLite."
 ---
@@ -14,6 +14,9 @@ compatibility: "Targets WordPress 6.9+ (PHP 7.2.24+). Playground CLI requires No
 - Build a reproducible snapshot of a site for sharing or CI.
 - Switch WP/PHP versions quickly to reproduce issues.
 - Debug plugin/theme code with Xdebug in an isolated Playground.
+- Run PHPUnit tests without a local database (no Docker, no MySQL).
+- Write E2E Playwright tests against a real WordPress instance.
+- Automate Playground in CI/CD pipelines via the programmatic `runCLI` API.
 
 ## Inputs required
 
@@ -82,6 +85,134 @@ npx @wp-playground/cli@latest build-snapshot --blueprint=<file> --outfile=./site
   - Query: `https://playground.wordpress.net/?blueprint-url=<public-url-or-zip>`
 - Use the live Blueprint Editor (playground.wordpress.net) to author blueprints with schema help; paste JSON and copy a shareable link.
 
+### 8) PHPUnit testing (no database required)
+
+Run PHPUnit inside Playground — every run starts with a clean WordPress install, fully isolated.
+
+Plugin:
+```bash
+npx @wp-playground/cli@latest php \
+  --auto-mount \
+  -- \
+  /wordpress/wp-content/plugins/MY_PLUGIN/vendor/bin/phpunit \
+  -c /wordpress/wp-content/plugins/MY_PLUGIN/phpunit.xml.dist
+```
+
+Theme (replace `plugins/` with `themes/`):
+```bash
+npx @wp-playground/cli@latest php \
+  --auto-mount \
+  -- \
+  /wordpress/wp-content/themes/MY_THEME/vendor/bin/phpunit \
+  -c /wordpress/wp-content/themes/MY_THEME/phpunit.xml.dist
+```
+
+- Requires PHPUnit installed via Composer in the project (`composer require --dev phpunit/phpunit`).
+- `--auto-mount` maps the current directory to the correct WP content path automatically.
+- Use `--php=8.1 --wp=6.5` flags to test against specific versions (PHP 7.4–8.5 supported).
+- Explicit mount: `--mount=.:/wordpress/wp-content/plugins/MY_PLUGIN`.
+
+### 9) E2E testing with Playwright
+
+Use `runCLI` from `@wp-playground/cli` to start a Playground server programmatically in Playwright tests. No Docker, no database.
+
+Install:
+```bash
+npm install --save-dev @playwright/test @wp-playground/cli
+npx playwright install chromium
+```
+
+Minimal `playwright.config.ts`:
+```ts
+import { defineConfig } from '@playwright/test';
+export default defineConfig({
+  testDir: './tests/e2e',
+  fullyParallel: false,
+  workers: 1,           // prevent port conflicts
+  timeout: 120_000,     // WP boot takes time
+  expect: { timeout: 30_000 },
+  use: { screenshot: 'only-on-failure', trace: 'on-first-retry' },
+});
+```
+
+First test (`tests/e2e/plugin.spec.ts`):
+```ts
+import { test, expect } from '@playwright/test';
+import { runCLI } from '@wp-playground/cli';
+
+let cli: Awaited<ReturnType<typeof runCLI>>;
+
+test.beforeAll(async () => {
+  cli = await runCLI({
+    command: 'server',
+    blueprint: {
+      preferredVersions: { php: '8.3', wp: 'latest' },
+      login: true,
+    },
+  });
+});
+
+test.afterAll(async () => { await cli?.server?.close(); });
+
+test('dashboard loads', async ({ page }) => {
+  await page.goto(`${cli.serverUrl}/wp-admin/`);
+  await expect(page.locator('#wpbody-content')).toBeVisible();
+});
+```
+
+Mount a local plugin:
+```ts
+cli = await runCLI({
+  command: 'server',
+  mount: { './': '/wordpress/wp-content/plugins/my-plugin' },
+  blueprint: {
+    preferredVersions: { php: '8.3', wp: 'latest' },
+    login: true,
+    steps: [{ step: 'activatePlugin', pluginPath: 'my-plugin/my-plugin.php' }],
+  },
+});
+```
+
+Locator priority (most to least preferred):
+1. `page.getByRole()` — buttons, headings, links, inputs
+2. `page.getByLabel()` — labeled form fields
+3. `page.getByText()` — visible text
+4. `page.getByTestId()` — your own `data-testid` attributes
+5. `page.locator()` — CSS/XPath last resort (WP core layout elements like `#wpadminbar`)
+
+Version matrix pattern:
+```ts
+const matrix = [{ php: '8.1', wp: '6.5' }, { php: '8.3', wp: 'latest' }];
+for (const { php, wp } of matrix) {
+  test.describe(`PHP ${php} + WP ${wp}`, () => {
+    // ... beforeAll/afterAll with those versions
+  });
+}
+```
+
+CI (GitHub Actions): see `references/e2e-playwright.md`.
+
+### 10) Programmatic `runCLI` API (scripts / Vitest integration)
+
+```ts
+import { runCLI } from '@wp-playground/cli';
+
+const server = await runCLI({
+  command: 'server',
+  php: '8.3',
+  wp: 'latest',
+  login: true,
+  mount: [{ hostPath: './my-plugin', vfsPath: '/wordpress/wp-content/plugins/my-plugin' }],
+  blueprint: { steps: [{ step: 'activatePlugin', pluginPath: 'my-plugin/plugin.php' }] },
+});
+
+// server.serverUrl — the base URL
+// server.server — the HTTP server instance (call .close() in afterEach)
+// server[Symbol.asyncDispose]() — cleanup in Vitest afterEach
+```
+
+Use `wordpressInstallMode: 'do-not-attempt-installing'` + `skipSqliteSetup: true` when testing pure PHP with no WordPress overhead.
+
 ## Verification
 
 - Verify mounted code is active (plugin listed/active; theme selected).

package/.github/skills/wp-playground/references/e2e-playwright.md

@@ -0,0 +1,115 @@
+# E2E Testing with Playwright + WordPress Playground
+
+## Install
+
+```bash
+npm install --save-dev @playwright/test @wp-playground/cli
+npx playwright install chromium
+```
+
+## playwright.config.ts
+
+```ts
+import { defineConfig } from '@playwright/test';
+export default defineConfig({
+  testDir: './tests/e2e',
+  fullyParallel: false,
+  forbidOnly: !!process.env.CI,
+  retries: process.env.CI ? 2 : 0,
+  workers: 1,
+  reporter: 'html',
+  timeout: 120_000,
+  expect: { timeout: 30_000 },
+  use: { screenshot: 'only-on-failure', trace: 'on-first-retry' },
+});
+```
+
+## Server lifecycle
+
+**Shared** (faster, tests can affect each other — use for read-only tests):
+```ts
+test.beforeAll(async () => { cli = await runCLI({ command: 'server', blueprint }); });
+test.afterAll(async () => { await cli?.server?.close(); });
+```
+
+**Per-test** (isolated, slower — use when tests modify state):
+```ts
+test.beforeEach(async () => { cli = await runCLI({ command: 'server', blueprint }); });
+test.afterEach(async () => { await cli?.server?.close(); });
+```
+
+## Blueprint fixtures
+
+Installing from wordpress.org:
+```ts
+steps: [{ step: 'installPlugin', pluginData: { resource: 'wordpress.org/plugins', slug: 'contact-form-7' } }]
+```
+
+Creating content:
+```ts
+steps: [{ step: 'runPHP', code: `<?php require '/wordpress/wp-load.php'; wp_insert_post([...]);` }]
+```
+
+## WordPress-specific locator guidance
+
+- `page.getByRole('button', { name: 'Save Changes' })` — works for standard WP buttons
+- `page.getByLabel('API Key')` — works for labeled form fields
+- `page.locator('#wpadminbar')` — CSS required for WP core layout elements (no ARIA)
+- Add `data-testid` to your own plugin markup for stable selectors
+- Run `npx playwright codegen localhost:9400/wp-admin/` to auto-generate locators
+
+## Page Object Model
+
+```ts
+// tests/e2e/pages/plugin-settings.ts
+export class PluginSettingsPage {
+  constructor(readonly page: Page) {}
+  async goto(baseUrl: string) { await this.page.goto(`${baseUrl}/wp-admin/options-general.php?page=my-plugin`); }
+  async setApiKey(key: string) {
+    await this.page.getByLabel('API Key').fill(key);
+    await this.page.getByRole('button', { name: 'Save Changes' }).click();
+  }
+  async expectSaved() { await expect(this.page.getByText('Settings saved')).toBeVisible(); }
+}
+```
+
+## GitHub Actions CI
+
+```yaml
+name: E2E Tests
+on:
+  push: { branches: [main] }
+  pull_request: { branches: [main] }
+jobs:
+  e2e:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: 20, cache: 'npm' }
+      - run: npm ci
+      - uses: actions/cache@v4
+        id: playwright-cache
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-${{ hashFiles('package-lock.json') }}
+      - if: steps.playwright-cache.outputs.cache-hit != 'true'
+        run: npx playwright install chromium --with-deps
+      - run: npx playwright test
+      - uses: actions/upload-artifact@v4
+        if: ${{ !cancelled() }}
+        with: { name: playwright-report, path: playwright-report/, retention-days: 30 }
+```
+
+## Troubleshooting
+
+- **Timeout errors** — increase `timeout` in config; CI needs 120–180s
+- **Port conflicts** — don't hardcode ports; use `cli.serverUrl`
+- **Browser not found** — run `npx playwright install chromium`
+- **Passes locally, fails CI** — increase timeouts, ensure `workers: 1`
+- **Debug** — `npx playwright test --debug` or `--ui` for interactive mode
+
+## Docs
+
+- https://wordpress.github.io/wordpress-playground/guides/e2e-testing-with-playwright
+- https://wordpress.github.io/wordpress-playground/guides/programmatic-playground-cli