A release was invisible from inside the app. `git log` is the technical
record and there was no human one, so a member's first sign of a new
version was a screen that had moved — the boards, the calendar, the
column filter all arrived without anybody being told.

So: `Services/Changelog.cs`, a list of releases in plain language,
newest first, and a dialog that renders it. A sparkle appears in the
header when the version on screen is one this browser has not read
about, and is gone once the dialog has been opened; "What's new" stays
in the nav menu afterwards, carrying the one place in the app that names
the running version.

Three decisions worth stating.

**One source of truth, and it is not a CHANGELOG.md.** Two lists of the
same releases drift, and the one that drifts is the one nobody has open
while writing code. The entry is therefore part of the change rather
than part of the tag: it is written in the pull request that makes the
change and dated the day it lands, which is also the only date that
exists while the code is being written. The release skill now checks
before tagging that `Changelog.Latest.Version` is the version about to
be cut.

**Copy lives beside its version, not in the translation table.**
`Translations` would grow half a dozen keys per release whose only
structure was their names. `ChangelogRelease.Changes` is keyed by locale
exactly the way `Translations` is and falls back to English by the same
rule, and `ChangelogTests` re-imposes what the translation tests impose
on everything else — both languages, nothing blank, no "handle" — plus a
jargon guard, because this is the one piece of copy in the app whose
failure mode is sounding like a commit message.

**What each browser has read is localStorage**, like the theme and the
install nudge, not a column on Member: it says nothing about the person,
and a database write per device buys nothing. `HasUnseen` compares for
equality rather than order, so a rollback also announces itself — going
quiet exactly when a member most wants to know what moved would be the
worst of the available answers.

One trap, and prefs.spec.js caught it: excluding `.nav-whatsnew` from
`.board-user button:not(.nav-hamburger)` adds a second `:not()`, which
raises that selector above `.board-user .nav-pref-options button` and
paints a surface over the theme pills — all three then read as chosen.
The round icon button overrides those defaults from its own block
instead, the way `.nav-menu-install` does.

Verified: `dotnet test` (205 passing, 9 new), and Playwright against a
live stack — the new changelog.spec.js plus prefs, install, i18n, board,
mobile, filter and boards. Screenshots taken in light, dark and German,
on desktop and at 390px.

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

@@ -21,0 +27,4 @@
+// new" — which for a first visit is true.
+
+const CHANGELOG_KEY = 'ponente-changelog-seen';
+