docs(ui-theme): record 0.2.0 publish + adoption across all 3 apps (local feat branches)

components/ui-theme/GAPS.md

@@ -3,6 +3,23 @@
 Divergence of each project from [`spec/SPEC.md`](spec/SPEC.md), and the ordered backlog to
 reach adoption of the `ZB.MOM.WW.Theme` shared RCL. Status legend: ⛔ gap · 🟡 partial · ✅ matches.
 
+> **✅ ADOPTED 2026-06-03 (local-only).** Backlog #2–#4 implemented across all three apps on each repo's
+> **`feat/adopt-zb-theme`** branch — full canonical cutover (SPEC §7): `<ThemeHead/>`/`<ThemeScripts/>`,
+> thin `MainLayout` → `<ThemeShell>` + `NavRailItem`/`NavRailSection`, per-app `theme.css`/IBM-Plex fonts/
+> `nav-state.js` deleted, `<LoginCard>` sign-in, and `StatusPill` (OtOpcUa's dead `StatusBadge` deleted;
+> MxGateway's `StatusBadge` redirected to a thin `StatusPill` adapter; inline domain `.chip-*` kept as page
+> content per §6). **Library first enhanced to `0.2.0`** — nav-expand persistence promoted INTO the kit
+> (`NavRailSection.Key` → `data-nav-key` + a localStorage `nav-state.js` enhancer emitted by a new
+> `<ThemeScripts/>`), so all three apps get uniform persistence from one source (OtOpcUa's bespoke
+> cookie/JS-interop nav island retired). 0.2.0 published to the Gitea feed; 44 bUnit tests. **MxGateway
+> additionally gained a net-new Blazor `<LoginCard>` `/login` page** reusing its existing hardened
+> `POST /login` endpoint (antiforgery + `SanitizeReturnUrl` + `SignInAsync` preserved). Every task spec+code
+> reviewed (high-risk via serial spec→code; the MxGateway login via an Opus security review). Branch heads:
+> OtOpcUa `11de14d`, ScadaBridge `58352a6`, MxGateway `73e54e2` — **committed local-only, not yet merged/pushed**.
+> Plan: `docs/plans/2026-06-03-ui-theme-adoption*.md`. The ⛔/🟡 cells below describe the PRE-adoption
+> divergence (kept for history). Deferred follow-ups: prune now-dead `.sidebar`/`.nav-link` residual from each
+> app's kept `site.css`; a kit-side `layout.css` `calc(100vh - 3.3rem)` review.
+
 ---
 
 ## Divergence vs spec