{
  "id": "e2e-remote",
  "command": "e2e-remote --server \"<dev-server-cmd>\" --wait-port <port> -- <browser-driver-cmd>",
  "summary": "Runs a dev server + browser-driving script as one coupled pair on a buildbox (SSH lane) or as a run-owned k3s Job (--k8s lane), and brings artifacts back.",
  "intent_phrases": ["run playwright tests", "take screenshots of the dev server", "run an e2e browser test", "visual diff the UI", "run e2e on k3s", "run e2e in kubernetes"],
  "replaces": ["astro dev & node shoot.mjs", "pnpm exec playwright test run locally", "e2e-k8s-dispatch invoked directly"],
  "preconditions": "SSH lane: server command must bind --host 127.0.0.1; artifacts written inside the repo tree. --k8s lane: the Job owns the server stack, so --server/--wait-port are ignored; run from the project checkout so the mirror slug resolves.",
  "effects": "SSH lane starts the dev server and browser driver together on a registry buildbox and rsyncs artifacts back. --k8s submits a run-owned Job in namespace ipz-e2e with label-scoped cleanup on every exit path.",
  "risk": "reversible",
  "example": "e2e-remote --k8s --env WP_BASE_URL=http://127.0.0.1:8080 -- pnpm --dir . exec playwright test --config=playwright.config.js --project=chromium",
  "help_probe": "e2e-remote --help"
}