Stage 5: wire the skin switch — both UIs now reachable

The reunion is complete: one build contains both UIs and picks between them at
bootstrap.

- src/shared/types.ts regains `skin: "modern" | "win7"` on AppSettings.
- SettingsService regains the skin signal, setSkin() and applySkin(), which
  toggles the `.win7` class on <html>.
- buildPreload emits __APP_SKIN and adds `.win7` conditionally again, instead
  of unconditionally as it had since fe028a9.
- chromeOptions() regains its parameter: win7 gets frameless + transparent,
  modern gets the macOS hiddenInset fusion or the plain native frame.
- core/platform.ts regains APP_SKIN / IS_WIN7_CHROME (added in stage 4).
- main.ts now selects on both axes — skin picks the tree, APP_MODE picks the
  root within it.
- Both tab-bars get a skin row, with the reopen caveat as its tooltip.

DEFAULT_SETTINGS.skin is "modern", matching the original design and `main`.
Worth flagging: this branch has booted win7 unconditionally since fe028a9, so
after this commit it starts in the modern UI unless the setting says otherwise.
One word in types.ts flips that if the win7 look should be the default.

i18n: en.ts is the source of truth and everything else falls back to it, so
only en was strictly required — but es/eu/fr/de/zh/ja got real translations
too, each matching the terminology that locale already uses for the Theme row.

Verified both skins on live single-instance captures. Modern boots and renders
fully styled, which also proves Tailwind scans skins/shadlike/** — a purge
would have produced an unstyled page rather than this one. Win7, selected by
setting skin in the persisted settings, is still pixel-identical to the
pre-refactor baseline across all five stages. The persisted settings file was
backed up and restored, so it still carries no skin key and resolves to the
default through the backend's merge.

Not verified: clicking the new skin row itself, which needs an interaction pass
— no window automation is available here. Its bindings compile and the built
bundle contains options.skin, setSkin and the translated labels.

Co-Authored-By: Claude <noreply@anthropic.com>

src/shared/types.ts

@@ -78,6 +78,18 @@ export type AccentTone =
 export interface AppSettings {
 	/** UI language; "system" resolves to the OS locale (fallback English). */
 	locale: "system" | SupportedLocale;
+	/**
+	 * Visual skin. "modern" is the shadcn-style look; "win7" swaps in 7.css
+	 * (Windows 7 Aero) and switches the window to custom frameless chrome.
+	 * Each skin is a whole component tree under ui/src/app/skins/ — "modern" is
+	 * shadlike/, "win7" is 7like/ — selected at bootstrap in ui/src/main.ts.
+	 * The value is NOT named after its folder on purpose: it is persisted in
+	 * user settings, and "win7" is also the literal class 7.scoped.css is
+	 * precompiled to require, so neither can be renamed freely.
+	 * Changing this needs a window reopen to take effect on the frame itself —
+	 * the CSS half applies live.
+	 */
+	skin: "modern" | "win7";
 	theme: "system" | "light" | "dark";
 	/** Dark appearance: grey ("dark") or near-black AMOLED ("darker"). */
 	darkTone: "dark" | "darker";
@@ -108,6 +120,7 @@ export interface AppSettings {
 
 export const DEFAULT_SETTINGS: AppSettings = {
 	locale: "system",
+	skin: "modern",
 	theme: "system",
 	darkTone: "dark",
 	accent: "blue",