VK moderation follow-ups.
1. Settings (theme, language, board style, reduce-motion, zoom, first-run
coachmark flags) were lost between reloads in VK's desktop iframe: Firefox
partitions/blocks IndexedDB and localStorage in a cross-origin iframe, so the
browser-local store is empty on every reload (a plain tab / PWA keeps them —
first-party storage — and Telegram has its own CloudStorage sync). Mirror the
prefs (plus the locale, which has no other durable client home on VK) and the
coachmark flags to VK Bridge storage (VKWebAppStorageSet/Get), which travels
over postMessage to vk.com and survives; reconcile them on the VK launch
before the first paint. The VK identity re-derives from the signed launch
params each load, so the values reload onto the same account.
2. Inside a proprietary Mini App host (VK or Telegram) the profile now surfaces
only email linking — both the Telegram and VK link/unlink entries are hidden
(signInProvidersVisible), so a competing sign-in is never advertised (a
platform ToS requirement; VK forbids showing a Telegram login, mirrored in
Telegram for VK). A provider linked earlier on the web stays attached and is
managed from the web; web/native builds show both.
Tests: vkprefs codec + signInProvidersVisible unit tests. Docs: ARCHITECTURE,
FUNCTIONAL (+_ru). No schema/wire change.
Ilia Denisov