[Client] Use wordpressInstallMode for Playground boot

[ashfame]

What it does

Uses wordpressInstallMode as the single boot control for WordPress installation and PHP-only Playground sessions.

Breaking change: shouldBootWordPress is removed from the client and worker boot options. Use wordpressInstallMode: 'do-not-attempt-installing' to skip WordPress boot setup.

Rationale

shouldInstallWordPress and shouldBootWordPress split one decision across two booleans and make PHP-only boot paths harder to reason about. wordpressInstallMode already names the behavior directly:

• download-and-install for fresh WordPress installs
• install-from-existing-files-if-needed for saved or mounted WordPress files
• do-not-attempt-installing for PHP-only sessions

Implementation

The Blueprints v1 client resolves a concrete wordpressInstallMode before booting the remote worker. Inline Blueprints with preferredVersions.wp: false resolve to do-not-attempt-installing unless the caller explicitly requested WordPress, in which case the handler throws a conflict error.

Website and Personal WP boot clients now pass wordpressInstallMode directly. The remote worker uses that mode to decide whether to download WordPress, run WordPress setup, or stop after mounting a PHP-only runtime.

shouldInstallWordPress remains accepted for compatibility, but is deprecated and translated into wordpressInstallMode.

Testing instructions

npm exec nx -- test playground-client --testFile=blueprints-v1-handler.spec.ts
npm exec nx -- test playground-remote --testFile=playground-worker-endpoint-blueprints-v1.spec.ts
npm exec nx -- run-many -t typecheck --projects=playground-client,playground-remote,playground-website,playground-personal-wp

[adamziel]

Thank you! We should also completely remove any trace of shouldBootWordPress and just rely on wordpressInstallMode: "do-not-attempt-installing".

[adamziel]

we don't need a helper method, this could be just a const

[akirk]

I tend agree but more for the reason that the helper method has the same complex boolean expression that could have been inserted here. What about we keep the helper method but change the boolean expression to simple ones with return statements.?

[adamziel]

Let's see what that expression looks like once there's no more shouldBootWordPress – I feel like it complicates the data flow.

[adamziel]

That seems not great and not terrible now. I'll go ahead and merge. We can keep iterating in a follow-up but I want to get rid of shouldBootWordPress before people start to use it.

[akirk]

From my perspective we can make this ready for review.

[adamziel]

@akirk we're already reviewing it anyway :-)

[adamziel]

@ashfame poke