Document E2E rerun blockers for CI-style bootstrap path

[Copilot]

This update addresses the request to rerun E2E using the CI bootstrap path (DOCKER_FILE=docker-compose.ci.yml bash bin/wp-init.sh) and Playwright. The run reproduces two environment-level blockers that currently prevent E2E execution.

• What this PR changes

  • Captures the current failure point in bin/wp-init.sh bootstrap:
    • DB readiness loop never completes because the CLI container cannot resolve mysql host.
  • Captures the direct Playwright blocker with the requested command sequence:
    • npm run test:e2e:playwright fails immediately because wp-scripts is unavailable in the current environment.
  • Keeps repository code untouched (execution-only diagnosis).

• Observed failure signatures

  • wp-init.sh path:
    • mariadb-check: Got error: 2005: Unknown server host 'mysql' (-3) when trying to connect
  • Playwright path:
    • sh: 1: wp-scripts: not found

• Reproduction commands

  DOCKER_FILE=docker-compose.ci.yml bash bin/wp-init.sh
  npm run test:e2e:playwright

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• 127.0.0.11
  • Triggering command: REDACTED, pid is -1 (packet block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.