# Yoast compatibility defect handoff

Owner: ACF/Yoast reconciliation lane
Source lane: PG-38..PG-42 compatibility preparation
Baseline: `origin/master` `feffca5bd8c00949b264a60adffaa0ab5afe8218`

## Minimal reproduction

Use the isolated compatibility orchestration; do not modify `tests/e2e/remote-stack.sh`:

```bash
IPZ_E2E_RUN_ID is supplied through e2e-remote:
e2e-remote \
  --server tests/e2e/remote-stack.sh \
  --wait-port 8080 \
  --env WP_BASE_URL=http://127.0.0.1:8080 \
  --env IPZ_E2E_RUN_ID=compat-yoast-256-chromium \
  -- tests/e2e/compatibility/with-yoast.sh chromium
```

`with-yoast.sh` installs Yoast SEO 25.6 into the disposable WP 6.6 stack, activates it, prints its exact version/status, then runs only `Yoast active: real SEO fields appear and admin/frontend remain clean`.

## Observed failure

- Yoast 25.6 installs and activates successfully on WordPress 6.6.
- The compatibility test then POSTs a representative published post through `/wp-json/wp/v2/posts`.
- Response is HTTP 500 instead of 201, before the IPZ SEO-field read assertion can run.
- Earlier vanilla/Yoast-absent content creation on the same sanctioned fixture passes.
- No ACF/Yoast/IPZ production files were changed by this lane.

The retained test now includes the REST response body in its assertion message on the next successful repro run. At handoff time, further collection was blocked by the remote-runner prerequisite defect that incorrectly requires `international-press-zone/node_modules/.bin/playwright` instead of the sanctioned `tests/e2e` Playwright installation.

## Required owner action

Reproduce after the remote runner is healthy, capture the exact HTTP 500 body/PHP error, determine whether the failure is Yoast initialization, fixture orchestration, or IPZ interaction, fix only in the owning lane if it is an IPZ defect, and rerun both Chromium and Firefox. Do not convert this provisional failure into PG-40 sign-off until the exact final RC passes.