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>

tests/unit/test_scheduler.py

@@ -68,7 +68,7 @@ class TestResumeTickers:
 
 
 class TestConfigureScheduler:
-    def test_configure_adds_six_jobs(self):
+    def test_configure_adds_all_jobs(self):
         # Remove any existing jobs first
         scheduler.remove_all_jobs()
         configure_scheduler()
@@ -81,6 +81,7 @@ class TestConfigureScheduler:
             "rr_scanner",
             "ticker_universe_sync",
             "outcome_evaluator",
+            "alerts",
         }
 
     def test_configure_is_idempotent(self):
@@ -90,6 +91,7 @@ class TestConfigureScheduler:
         job_ids = [j.id for j in scheduler.get_jobs()]
         # Each ID should appear exactly once
         assert sorted(job_ids) == sorted([
+            "alerts",
             "data_collector",
             "fundamental_collector",
             "outcome_evaluator",