Fix Studio app metadata for Linux software stores (#3335)

## Related issues

- Fixes
[RSM-1313](https://linear.app/a8c/issue/RSM-1313/fix-studio-app-description-in-the-stores-on-linux-systems)

## How AI was used in this PR

Used AI to:
- Pull the canonical Microsoft Store description copy from the Store API
and adapt it for the Linux package metadata.
- Walk through electron-installer-debian's defaults and template logic
to identify why the synopsis and extended description were duplicating
in the .deb control file.

I reviewed each diff and pushed back on changes I didn't think were
right (e.g. an earlier draft used `genericName` for `Name=`, which
mismatched the runtime WMClass).

## Proposed Changes

- **`forge.config.ts` MakerDeb options**: set explicit `productName:
'WordPress Studio'` and `description` (synopsis) + `productDescription`
(long, mirrors MS Store copy in ASCII-safe punctuation). Without these,
both fields fall back to `package.json.description`, producing a
duplicated Description block.
- **`desktop.ejs`**: hardcode `StartupWMClass=Studio` so the launcher
entry stays linked to Electron's runtime WMClass even though `Name=` is
now `WordPress Studio`. Without this, the launcher icon would not group
with the running window.

## Testing Instructions

On a Linux VM:

1. Build the .deb: `npm run make`.
2. Purge any prior install (for a clean slate): `sudo apt purge studio`.
3. Verify package metadata:
   - `dpkg-deb -I apps/studio/out/make/deb/<arch>/studio_*.deb`
- `dpkg-deb --fsys-tarfile apps/studio/out/make/deb/<arch>/studio_*.deb
| tar -xO ./usr/share/applications/studio.desktop`
4. Confirm title and description in the output above:
- control `Description:` — new synopsis ("Meet Studio - ...") followed
by the 3-paragraph long description.
- `.desktop` — `Name=WordPress Studio`, `Comment=Meet Studio - ...`,
`StartupWMClass=Studio`.
5. Open the .deb in the app center (double-click in Files, or `xdg-open
apps/studio/out/make/deb/<arch>/studio_*.deb`).
6. Confirm title and description in the app center preview match the new
copy. (See Known limitation re: title.)

<img width="1926" height="1536" alt="CleanShot 2026-05-04 at 22 37
20@2x"
src="https://github.com/user-attachments/assets/a837549d-fa30-482b-afaa-596cf6d7df71"
/>

### Known limitation

The pre-install software-store preview shows the lowercase Debian
package name (`studio`) as the title, not `WordPress Studio`.
PackageKit's local-deb plugin doesn't read AppStream metainfo from
inside .deb files, only the control fields, and `Package:` must be
lowercase per Debian policy. Renaming the package to `wordpress-studio`
would address this but cascades into install paths, postinst probes, and
`rc`-state migrations for users with existing `studio` installs —
leaving for a follow-up issue.

## Pre-merge Checklist

- [ ] Verified the rebuilt .deb's control + .desktop files
- [ ] Verified software-store listing renders proper metadata after
install

Author: gavande1

apps/studio/forge.config.ts

@@ -82,10 +82,20 @@ const config: ForgeConfig = {
 		new MakerZIP( {}, [ 'darwin' ] ),
 		new MakerDeb( {
 			options: {
-				genericName: 'WordPress Studio',
+				// Display name for app launchers and stores. Overrides
+				// package.json.productName ("Studio") so Linux users see the
+				// fully-qualified "WordPress Studio" in their menus.
+				productName: 'WordPress Studio',
 				categories: [ 'Utility' ],
 				name: 'studio',
 				bin: 'studio',
+				// Synopsis and extended description shown by package managers and
+				// software stores. Without these, electron-installer-debian falls
+				// back to package.json.description for both, producing a duplicated
+				// Description block. Copy mirrors the Microsoft Store listing.
+				description: 'Meet Studio - a fast, free way to develop locally with WordPress.',
+				productDescription:
+					"Simplify WordPress site creation and management with Studio - WordPress.com's powerful, lightweight local development tool. Studio streamlines your workflow with instant WordPress setup, one-click WP Admin access, and a code-agnostic environment. No Docker, MySQL, or NGINX required. Get real-time feedback from clients or collaborators with easy-to-share demo sites. And with help from Studio Assistant, you can speed up plugin management, run WP-CLI commands, and automate tasks right from the intuitive chat interface.",
 				mimeType: [ 'x-scheme-handler/wp-studio' ],
 				icon: path.join( __dirname, 'assets', 'studio-app-icon.png' ),
 				desktopTemplate: path.join( __dirname, 'installers', 'desktop.ejs' ),

apps/studio/installers/desktop.ejs

@@ -6,7 +6,9 @@
 Icon=<%= name %>
 <% } %>Type=Application
 StartupNotify=true
-StartupWMClass=<%= productName %>
+# Must match Electron's runtime WMClass (derived from app.getName(), i.e. package.json.name).
+# Don't template from productName — the launcher icon won't group with the running window.
+StartupWMClass=Studio
 <% if (categories && categories.length) { %>Categories=<%= categories.join(';') %>;
 <% } %><% if (mimeType && mimeType.length) { %>MimeType=<%= mimeType.join(';') %>;
 <% } %>

apps/studio/package.json

@@ -5,6 +5,7 @@
 	"productName": "Studio",
 	"version": "1.8.2",
 	"description": "Local WordPress development environment using Playgrounds",
+	"homepage": "https://developer.wordpress.com/studio/",
 	"license": "GPL-2.0-or-later",
 	"main": "dist/main/index.js",
 	"config": {