feat(legal): host the privacy policy and EULA at /privacy/ and /eula/

Author ui/legal/{privacy,eula}_ru.md, reworked from the source documents: the seller INN is unified (290210610742), contacts unified to the Telegram bot + email + postal address, the EULA governing-law clause leads with Russian law + jurisdiction as residence tiers, the single-binding-language clause is dropped, data collection is scoped to voluntary/support provision, and "Компания" is no longer shout-cased.

Serve both as static pages through the render sidecar, reusing a shared renderLegalHtml generalised from renderOfferHtml: new GET /privacy/ and GET /eula/ (301 from the slashless form), the markdown baked into the image, no backend fetch. Route them at the edge via the @legal caddy matcher with a CI probe asserting each page's canonical URL + the seller INN, so a missing route cannot silently fall through to the landing. Add the two links to the landing footer.

Docs baked in: ARCHITECTURE (renderer legal pages + edge routing), FUNCTIONAL (+_ru) footer, renderer/README routes. Tests: renderer legal.test.mjs, ui renderLegalHtml unit, landing footer e2e.

ui/src/lib/i18n/en.ts

@@ -286,6 +286,8 @@ export const en = {
   'landing.captionTelegram': 'Telegram',
   'landing.captionVK': 'VK',
   'landing.captionWeb': 'Web',
+  'landing.eula': 'Terms of Use',
+  'landing.privacy': 'Privacy Policy',
   'landing.offer': 'Public offer',
   'landing.feedback': 'Feedback',
 

ui/src/lib/i18n/ru.ts

@@ -286,6 +286,8 @@ export const ru: Record<MessageKey, string> = {
   'landing.captionTelegram': 'Telegram',
   'landing.captionVK': 'VK',
   'landing.captionWeb': 'Веб-версия',
+  'landing.eula': 'Пользовательское соглашение',
+  'landing.privacy': 'Политика конфиденциальности',
   'landing.offer': 'Публичная оферта',
   'landing.feedback': 'Обратная связь',