[lippdev]

What

The owner wants 1.7.0 to ship with a Legacy download in the same release: Console Mode 1.6.2 as it is (Desktop and Console interfaces), for anyone who misses the old interface, frozen for good. This branch (release/1.7-legacy, cut from v1.6.2) is that build; the release workflow on main will build it next to the normal one.

Three changes on top of 1.6.2, nothing else:

• Keeps the current app's settings. 1.7 writes 16 settings 1.6.2 doesn't have (custom apps, per-game profiles, the opening, pointer parking, the Task View shortcut...). 1.6.2 read the file fine but dropped them on its next save. AppConfig.NewerSettings ([JsonExtensionData]) keeps them and BuildConfig hands them back. A launcher only 1.7 has (customApp:<id>) is also written back as it came, unless another launcher is picked in Legacy; Steam Big Picture shows and opens meanwhile, as 1.6.2 already did for an unknown value.
• Never checks for updates (AppEdition.ChecksForUpdates), and the three update rows are collapsed in Settings and in the Console interface. checkUpdates / betaUpdates stay in the file for the current app.
• Calls itself Legacy: version 1.7.0, "Console Mode Legacy" in the window title, tray tooltip, Settings ("1.7.0 Legacy"), the startup log line and the installer (AppVerName, uninstall entry). Same AppId and data folder: it installs over the current app and the current app installs back over it.

Verified on the owner's PC (debug build, portable data, no session started)

A copy of the owner's 1.7 config, made safe (game screen = the primary one, nothing hidden) and given two custom apps, a game profile and fullscreenMode: customApp:a1:

• Legacy opens as "Console Mode Legacy", the pipe answers version 1.7.0, the log has no update check.
• Skipping its first-run tour saves the file: 50 keys in, 52 out (uiMode and tourDone are its own), none lost, and all 17 compared values identical, fullscreenMode included.
• dotnet test: 414 passing (3 new in LegacyConfigTests).

🤖 Generated with Claude Code

[pullfrog]

✅ No new issues found.

Reviewed changes This review covers the Legacy edition changes, including config preservation, update-check suppression, Legacy branding, and associated tests.

• Config compatibility: Preserves settings and custom launch modes unknown to Legacy when saving the shared config.
• Legacy behavior and branding: Suppresses startup update checks, hides update controls, and identifies the build as Legacy in the app and installer.
• Coverage and release notes: Adds config round-trip tests and documents the Legacy release in both changelogs.

  ^{｜ View workflow run ｜ Using gpt-6-luna ｜ 𝕏}