Accept --wp auto-update as the CLI name for the auto-update mode

[gcsecsey]

Related issues

• Related to STU-2348
• Stacked on Set the right expectation for the "latest" WordPress version setting #4702

How AI was used in this PR

I used Opus 5 for implementation and tests.

Proposed Changes

#4702 renames the "latest" WordPress version option to "Auto-update" in both UIs. This PR updates the naming in the CLI to keep it consistent.

--wp auto-update now selects that mode, matching what the apps show. --wp latest keeps working as an alias too, so existing scripts and blueprints are unaffected.

latest is still the internal value, and it still names a cache directory, a segment of the wordpress.org download URL, and the persisted site setting. The alias is resolved where the CLI parses input and never reaches storage.

Two side effects:

• blueprint use --wp was not validated at all. It needed the alias mapping anyway, and the shared coercion brings validation with it, so a bad value now fails at parse time instead of throwing from inside the download helper.
• The interactive version picker in site create said latest (7.1); it now says Auto-update (7.1), matching the apps.

Testing Instructions

• Build the CLI with npm run cli:build

The new value works

node apps/cli/dist/cli/main.mjs site create --path ~/Studio/wp-alias --name wp-alias --wp auto-update --no-start

• check ~/.studio/cli.json: the site should have "isWpAutoUpdating": true.

latest still works

node apps/cli/dist/cli/main.mjs site start --path ~/Studio/wp-alias
node apps/cli/dist/cli/main.mjs config set --path ~/Studio/wp-alias --wp 6.9
node apps/cli/dist/cli/main.mjs config set --path ~/Studio/wp-alias --wp latest

--wp 6.9	--wp latest

isWpAutoUpdating should go false, then back to true. The site has to be running
for config set --wp to apply, so studio start it first.

Help text

site create --help, config set --help and blueprint use --help should all
describe auto-update and mention that latest is accepted.

Pre-merge Checklist

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

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

🟡 Changes recommended

The agent-facing skill update lacks required eval coverage, and its validation message omits the supported latest alias.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 2
• Review effort level: Balanced