---
description: Load canonical IPZ remote E2E contract
---

Audience: AI coding agents first. Execute `/ipz-e2e` only through canonical contract below. `tests/e2e/remote-stack.sh` MUST, on same authorized buildbox and before WordPress container mount/readiness, resolve absolute npm/node entrypoints, run locked `admin/package-lock.json` dependencies through direct `npm ci`, run established `npm run build`, and fail closed unless `admin/dist/asset-manifest.json` plus required assets exist. NEVER select Bun, shell-route npm, locally build, or commit generated `admin/dist`. Fresh stack MUST provision postname permalinks, writable Apache `.htaccess`, flushed rewrite rules, and unauthenticated `/wp-json/` JSON routing before delayed port publication. HTML from `/wp-json/` is rewrite provisioning failure, NOT product JSON bug. Playwright raw artifacts remain `tests/e2e/test-results`; HTML report is distinct `tests/e2e/playwright-report`; JUnit is `tests/e2e/test-results/junit.xml`. For zero group disclosures with valid fixture, first use canonical failure ladder to prove remote candidate manifest/assets and browser-loaded bundle. Use canonical absolute pnpm client seam; path/version MUST update with environment changes. Preserve exact-label ownership and cleanup rules from canonical skill.

!.claude/skills/ipz-e2e.md