feat: T4 wave 11 – bottling form with article values and confirmation, Telegram in the app

- Bottling form: jar size and best-before from the product with source,
  differs-hints before saving, prefill status, water-content confirmation
  naming the measured value, idempotency key renewed on body change;
  product form gets shelf life (months) and whole-gram jar weight.
- Telegram frontend: link card with step-up dialog, t.me-only deep link,
  status polling, unlink; system Telegram card with receiver/sender state
  and confirmed retry; StepUpDialog shared with the backup import.
- Reauth calls never refresh-and-retry on 401 (no double lockout count);
  German texts for expired session and 429; service worker never caches
  Telegram, notification settings and system responses.
- Telegram backend round 2: shared link removal on every disconnect path,
  lease released on shutdown, connection errors not counted as poison.
- ARCHITECTURE.md §2, §6 (Annahmen 56–58), §10, §11.12, §11.13; TASKS.md T4.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

ApiCore-Frontend/src/lib/notifications/labels.ts

@@ -0,0 +1,14 @@
+import type { NotificationCategory } from "./types";
+
+export const NOTIFICATION_CATEGORY_LABELS: Record<NotificationCategory, string> = {
+  TASK_DUE: "Aufgaben fällig",
+  DIGEST: "Morgenübersicht",
+  SUGGESTION: "Vorschläge",
+  WITHDRAWAL: "Wartezeit",
+  SEASON: "Saison",
+  SYSTEM: "System",
+};
+
+export const NOTIFICATION_CATEGORIES = Object.keys(
+  NOTIFICATION_CATEGORY_LABELS,
+) as NotificationCategory[];