Split the WordPress version setting into an update mode and a version picker

[gcsecsey]

Related issues

• Related to STU-2348
• Stacked on Accept --wp auto-update as the CLI name for the auto-update mode #4750
• Lifts the update-mode control from Design exploration: Clarify Agentic UI site settings #4747

How AI was used in this PR

I used Opus 5 for implementation and tests.

Proposed Changes

The WordPress version setting mixes two decisions: whether the site updates itself, and which version it is pinned to. #4702 fixes the wording of the single dropdown, but the two decisions still share one control.

This PR splits them into an Automatic updates toggle and a version picker that's only shown when the toggle is off, so the picker only ever means "pin this version". While auto-update is on, the field reports the version the site runs.

• Without a version list (no network, no cached versions) the control degrades to the old plain dropdown.
• Turning auto-update off seeds the picker with the version the site already runs, or with the newest stable release for a site that does not exist yet. Beta or nightly are never set as defaults.

Testing Instructions

• Open a site, then Settings
• Check that if Automatic updates is on, the field shows Installed version: <version>.
• Turn the toggle off
• Check that the Version picker appears, preselected to the version the site runs
• Pick another version and check that Save settings becomes enabled
• Go back, add a site, and open Advanced settings
• Check the same toggle, and that turning it off preselects the newest stable release

State	Light	Dark
Agentic UI settings auto-update
Agentic UI settings pinned version
Agentic UI new site auto-update
Agentic UI new site pinned version
Classic UI settings auto-update
Classic UI settings pinned version
Classic UI new site auto-update
Classic UI new site pinned version

Pre-merge Checklist

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

[Copilot]

🟡 Changes recommended

The automatic-update description is not programmatically associated with its radio control for screen-reader users.

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

Pull request overview

Splits the Agentic UI’s WordPress setting into update mode and pinned-version controls.

Changes:

• Adds automatic-update and version-selection radio choices.
• Handles unknown and unavailable versions safely.
• Adds responsive styling, dark-theme colors, and focused tests.

File summaries

File	Description
apps/ui/src/index.css	Styles radio controls across themes.
apps/ui/src/components/site-overview-view/index.test.tsx	Tests settings interactions and edge cases.
apps/ui/src/components/site-fields/wp-version-control.tsx	Implements the split controls.
apps/ui/src/components/site-fields/style.module.css	Lays out the new controls.
apps/ui/src/components/site-fields/index.ts	Builds current and unknown version options.
apps/ui/src/components/site-fields/index.test.ts	Tests generated version options.

Review details

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

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[shaunandrews]

I don't think the toggle switch works; it adds extra complexity, hiding and showing controls, along with the broken/janky layout when controls pop into row.

^^ That is not something I would be comfortable shipping.

--

I still strongly suggest the radio buttons, and avoiding the side-by-side rows:

I only showed the toggle option previously to rule it out; not entice implementation. Sorry about that.

[shaunandrews]

Mostly, we should be aiming towards an end state as shown in #4747

[wpmobilebot]

📊 Performance Test Results

Comparing fc37fea vs trunk

app-size

Metric	trunk	fc37fea	Diff	Change
App Size (Mac)	1426.01 MB	1425.97 MB	0.04 MB	⚪ 0.0%

site-editor

Metric	trunk	fc37fea	Diff	Change
load	1199 ms	1216 ms	+17 ms	⚪ 0.0%

site-startup

Metric	trunk	fc37fea	Diff	Change
siteCreation	7528 ms	7538 ms	+10 ms	⚪ 0.0%
siteStartup	3369 ms	3365 ms	4 ms	⚪ 0.0%

---

Results are median values from multiple test runs.

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

[gcsecsey]

@shaunandrews I updated the site settings pages and create site modals, to bring them closer to the end result you shared. WDYT about this layout?

Classic UI Edit site modal:

CleanShot.2026-09-03.at.18.35.38.mp4

Classic UI add site screen:

Agentic UI site settings pane:

narrow width	wide width

Agentic UI create site screen:

[wojtekn]

@gcsecsey I think this UI is much easier to understand. However, I would still display the version that will be installed, as now, it can surprise the user. Also, spacing between elements seems odd:

[shaunandrews]

Looks great! Some spacing issues:

There's all this extra white-space on the left/right that we don't need.

Can we clean up all of these different spacing values? We need to define a system.