Add Beta Features menu

[wojtekn]

Related issues

• Fixes STU-855

Proposed Changes

• Added "Beta Features" menu to the app menu (available for all users, not just dev builds)
• Beta features are disabled by default and saved in appdata-v1.json for cross-app/CLI access
• Exposed "Studio Sites CLI" as the first beta feature
• Updated CLI to check betaFeatures.studioSitesCli from appdata instead of ENABLE_CLI_V2 environment variable
• Added "(Beta)" label to studio site command when the beta feature is enabled

Windows	macOS

Testing Instructions

Testing the Beta Features Menu

1. Launch the Studio app
2. Open the app menu (Studio menu on macOS, or File menu on other platforms)
3. Find and click the "Beta Features" menu item
4. You should see the "Studio Sites CLI" checkbox (unchecked by default)

Testing CLI Integration

1. Build the CLI: npm run make
2. Run CLI without beta feature: node dist/cli/main.js --help
   • Verify site command is NOT listed
3. Enable beta feature in Studio app: Check "Beta Features → Studio Sites CLI"
4. Run CLI again: node dist/cli/main.js --help
   • Verify site Manage local sites (Beta) command is now listed
5. Test the command: node dist/cli/main.js site list
   • Should work if the beta feature is enabled

Verify Persistence

1. Enable "Studio Sites CLI" in the app
2. Quit and restart Studio
3. Open Beta Features menu - checkbox should remain checked
4. Check ~/Library/Application Support/Studio/appdata-v1.json (macOS) or equivalent
   • Should contain: "betaFeatures": { "studioSitesCli": true }

Pre-merge Checklist

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

[bcotrim]

Works as described and a nice addition in my opinion!
LGTM 👍

[wojtekn]

@bcotrim Thank you for your review. Your Feature Flags menu implementation paved the way. 🥳

[katinthehatsite]

Functionally, this works for me and I did not run into any issues 👍

I had one suggestion about the naming: to me, as a user with little context, it was not really clear what Studio Sites CLI did, especially since there was also Install CLI... command that was in the top menu. Perhaps we could improve the naming there

[wojtekn]

@katinthehatsite, do you see any short name we could use instead of the current one to make it more descriptive?

Alternatively, we could use the menu description. It looks like that on macOS:

I'm unsure how it works on Windows, though.

[github-actions]

📊 Performance Test Results

Comparing a9bfcfb vs trunk

site-editor

Metric	trunk	a9bfcfb	Diff	Change
load	10348.50 ms	10612.00 ms	+263.50 ms	🔴 2.5%

site-startup

Metric	trunk	a9bfcfb	Diff	Change
siteCreation	18140.00 ms	23252.00 ms	+5112.00 ms	🔴 28.2%
siteStartup	4942.00 ms	5934.00 ms	+992.00 ms	🔴 20.1%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change

[katinthehatsite]

Alternatively, we could use the menu description. It looks like that on macOS:

Oh I think this is very nice, let's do that. It would give users a brief idea of what the feature 👍 Worst case, we can try to limit it to Mac

[wojtekn]

I adjusted it for Windows, as it didn't look great with sublabel:

Before	After

[nightnei]

LGTM and works as expected. Left just a few NIT comments

[nightnei]

It seems we don't need it. Also we can remove it from FeatureFlags.

Suggested change

// eslint-disable-next-line @typescript-eslint/no-empty-object-type

[nightnei]

It seems it's not used outside

Suggested change

	export const BETA_FEATURES_DEFINITION: Record< keyof BetaFeatures, BetaFeatureDefinition > = {
	const BETA_FEATURES_DEFINITION: Record< keyof BetaFeatures, BetaFeatureDefinition > = {

[nightnei]

Suggested change

	export function buildBetaFeatures( userData: BetaFeatures | undefined ): BetaFeatures {
	function buildBetaFeatures( userData: BetaFeatures | undefined ): BetaFeatures {