Set WP_SQLITE_AST_DRIVER constant when running wp CLI commands without running server

[wojtekn]

Related issues

• N/A

How AI was used in this PR

I debugged the SQLite plugin issue popping up in Studio CLI when running wp command and identified an issue. Then, used Claude Code to implement the fix.

Proposed Changes

• Set WP_SQLITE_AST_DRIVER: true in runWpCliCommand() via php.defineConstant() to match what the WordPress server sets via blueprint constants on startup

When a Studio site server is running, wp CLI commands are forwarded to the already-running playground instance which has WP_SQLITE_AST_DRIVER: true active (set via blueprint constants in wordpress-server-child.ts). When no server is running, runWpCliCommand spawns a fresh PHP-WASM instance without a blueprint - so the constant was never set, causing the SQLite AST driver to be skipped.

Testing Instructions

1. Stop any running Studio server for a local site
2. Run a wp CLI command against that site: node apps/cli/dist/cli/main.mjs wp plugin list --path=<site-path>
3. Confirm the command succeeds

Pre-merge Checklist

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

[wpmobilebot]

📊 Performance Test Results

Comparing 5680a8b vs trunk

app-size

Metric	trunk	5680a8b	Diff	Change
App Size (Mac)	1263.82 MB	1263.82 MB	+0.00 MB	⚪ 0.0%

site-editor

Metric	trunk	5680a8b	Diff	Change
load	1913 ms	1939 ms	+26 ms	⚪ 0.0%

site-startup

Metric	trunk	5680a8b	Diff	Change
siteCreation	8174 ms	8194 ms	+20 ms	⚪ 0.0%
siteStartup	4884 ms	4944 ms	+60 ms	🔴 1.2%

---

Results are median values from multiple test runs.

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

[fredrikekelund]

Works great 👍

[katinthehatsite]

It looks good to me and the command succeeds: