add Telegram alerts: qualified setups, S/R proximity, score drops, daily digest

Closes the action loop — instead of polling the dashboard, the platform pushes
actionable signals to Telegram. New hourly 'alerts' job dispatches four
toggleable triggers, deduped via a new alert_log table (cooldown-based for
qualified/S-R/digest, watermark-based for score deterioration). Admin → Settings
gains a Telegram panel (write-only bot token, chat ID, per-trigger toggles, Send
Test). Credentials follow DB > env precedence (TELEGRAM_BOT_TOKEN / _CHAT_ID).

Backend: alert_service + AlertLog model + migration 005, scheduler job, admin
endpoints/schema. Frontend: AlertSettings panel, hooks, api, types.

Deploy: run alembic upgrade (new alert_log table).

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

frontend/src/lib/types.ts

@@ -179,6 +179,22 @@ export interface SentimentProviderConfig {
   custom_base_url_providers: string[];
 }
 
+export interface AlertConfig {
+  enabled: boolean;
+  telegram_chat_id: string;
+  bot_token_configured: boolean;
+  bot_token_source: 'database' | 'environment' | 'none';
+  qualified_enabled: boolean;
+  sr_proximity_enabled: boolean;
+  score_drop_enabled: boolean;
+  digest_enabled: boolean;
+}
+
+export interface AlertTestResult {
+  ok: boolean;
+  error?: string;
+}
+
 export interface SentimentTestResult {
   ok: boolean;
   provider: string;