0.2.99

v0.2.99

Bump to 0.2.99 -- 0.2.98's fix was wrong; real fix is startTransition…

0.2.98

v0.2.98

Bump to 0.2.98 -- root-caused the cold-boot Home lag: Framer Motion's…

0.2.97

Bump to 0.2.97 -- browsable per-game achievements list

Games only ever showed a bare X/Y achievements count. Adds a real
drill-in: press L3 (contextMenu, unused in this screen until now) on
a selected game's achievements row to open a scrollable list with each
achievement's icon (grayed out while locked), name, description, and
unlock date.

Backend merges two Steam Web API calls: GetSchemaForGame for the
static name/description/icon data (public, cached indefinitely on
disk since it never changes per-game) and GetPlayerAchievements for
the actual per-player achieved/unlockTime state (fetched fresh every
time, since that's what actually changes). Fetched lazily only when
the list is actually opened, not alongside the existing summary count
every game selection already pays for.

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

0.2.96

Bump to 0.2.96 -- temporary perf diagnostics for the cold-boot Home lag

The backdrop-blur fix (0.2.95) didn't fix the actual report: "laggy
when I open the app, fine on Home after visiting a page and back."
Backdrop-blur cost would be identical on every Home mount, so it can't
explain a first-mount-only symptom -- something is specifically
expensive on Home's very first paint of a session and never again.
Rather than guess a second time, this adds real measurement: times
each of Home's five mount-time IPC fetches, and runs a longtask
PerformanceObserver for the 8s after mount (Chromium's own "main
thread blocked 50ms+" signal, tagged first-mount vs remount so the two
can actually be compared. Reports one consolidated line per mount to
the existing persistent log (nexus.log) via logging.reportError, reused
purely as a log-write pipe -- doesn't raise the on-screen CrashToast.
Meant to be read back after one real repro on real hardware, then
removed once the actual bottleneck is identified.

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

0.2.95

v0.2.95

Bump to 0.2.95 -- Home's own panels were stacking backdrop-blur, the …

0.2.94

v0.2.94

Bump to 0.2.94 -- PS button restore was leaving Nexus windowed, not f…

0.2.93

v0.2.93

Bump to 0.2.93 -- gamepad loop can no longer die silently, fix card-g…

0.2.92

v0.2.92

Bump to 0.2.92 -- prevent Windows from power-throttling Nexus during …

0.2.91

v0.2.91

Bump to 0.2.91 -- plugins have a mouse-clickable way out, new getEnvV…

0.2.90

Bump to 0.2.90 -- Store's My Themes is display-only, built-ins excluded

My Themes was showing every theme (built-in and custom) as a tap-to-
apply control, duplicating what Settings > Appearance's theme accordion
already does properly -- two competing ways to activate a theme, and
the built-ins showing up in a "store" context never made sense (they're
not something you added, they're always there).

My Themes now lists only custom/installed themes, and is purely a
display of what you've got -- no click action, "Active" still shown as
information but "Tap to Apply" is gone. Activating, customizing,
submitting, or removing a theme all stay exactly where they already
are: Settings > Appearance. Community Themes (browse/install new ones)
is untouched.

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