Update Playground and PHP-WASM dependencies to 3.1.43

[wojtekn]

Related issues

• Related to https://github.com/WordPress/wordpress-playground/releases/tag/v3.1.43

How AI was used in this PR

AI bumped all @wp-playground/* and @php-wasm/* dependencies to the new release, regenerated the lockfile, and ran the verification suite (typecheck, CLI build, lockfile dedup check). The diff was reviewed for correctness.

Proposed Changes

• Updates WordPress Playground and PHP-WASM to v3.1.43 (from 3.1.38). This keeps Studio's bundled WordPress runtime current with upstream fixes and improvements. No user-facing behavior change is expected beyond what the upstream release provides.

All versions remain pinned exactly (no ^/~), and the lockfile resolves a single 3.1.43 copy of every Playground/PHP-WASM package — no duplicate nested copies that would bloat the bundle.

Testing Instructions

• npm install — confirms a clean install with all Playground/PHP-WASM packages resolved to 3.1.43.
• npm run typecheck — passes across all workspaces.
• npm run cli:build && node apps/cli/dist/cli/main.mjs --version — CLI builds and runs.
• Smoke-test creating and running a local site to confirm the runtime works end to end.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wpmobilebot]

📊 Performance Test Results

Comparing 2242844 vs trunk

app-size

Metric	trunk	2242844	Diff	Change
App Size (Mac)	1316.83 MB	1316.84 MB	+0.01 MB	⚪ 0.0%

site-editor

Metric	trunk	2242844	Diff	Change
load	1113 ms	732 ms	381 ms	🟢 -34.2%

site-startup

Metric	trunk	2242844	Diff	Change
siteCreation	6501 ms	6472 ms	29 ms	⚪ 0.0%
siteStartup	1862 ms	1862 ms	0 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

[epeicher]

Thanks for the upgrade @wojtekn! I have tested it, and I have not found any issues. I have tested running the CLI and creating and starting sites using Studio UI. LGTM!

Check version