rename class for kubernetes

Author: JustinGuese

LLM_README.md

@@ -69,7 +69,7 @@ The `Bot` class (`tradingbot/utils/botclass.py`) is the foundation. All trading
    - **Examples**:
      - `sharpePortfoliooptWeekly.py` (portfolio optimization with multiple assets)
      - `aihedgefundbot.py` (reads trading decisions from external database and rebalances)
-     - `telegram_signalsbankbot.py` (reads `telegram_messages` table, classifies signals via AI, partial buys at 20% of cash per signal; uses `acted_on` column for crash-safe deduplication)
+     - `telegramsignalsbankbot.py` (reads `telegram_messages` table, classifies signals via AI, partial buys at 20% of cash per signal; uses `acted_on` column for crash-safe deduplication)
 
 ### Bot Class Lifecycle
 

docs/api/telegram-monitor.md

@@ -43,7 +43,7 @@ class TelegramMessage(Base):
 
 **Constraints**:
 - Unique on `(channel, message_id)` — prevents duplicate storage
-- `acted_on` set atomically before AI classification in `telegram_signalsbankbot` — crash-safe
+- `acted_on` set atomically before AI classification in `telegramsignalsbankbot` — crash-safe
 
 **Indexes**: `(channel, published_at)`, `symbol`
 

docs/architecture/database-models.md

@@ -149,7 +149,7 @@ class TelegramMessage(Base):
 **Unique constraint**: `(channel, message_id)` — same message never stored twice.
 **Indexes**: `(channel, published_at)`, `symbol` — efficient queries by symbol or channel timeline.
 
-`acted_on` is set to `True` by `telegram_signalsbankbot` **before** the AI classification call — crash-safe deduplication without a separate tracking table.
+`acted_on` is set to `True` by `telegramsignalsbankbot` **before** the AI classification call — crash-safe deduplication without a separate tracking table.
 
 See [Telegram Monitor Guide](../guides/telegram-monitor.md) and [Telegram Signals Bot Guide](../guides/telegram-signals-bot.md) for setup and usage.
 

docs/guides/telegram-monitor.md

@@ -296,7 +296,7 @@ tradingbot/utils/telegram_monitor.py   (implementation)
 └── get_existing_message_ids()      → Deduplication
 ```
 
-Runs as a stateless CronJob — no persistent connection. Downstream, `telegram_signalsbankbot` reads the stored messages and acts on signals. See [Telegram Signals Bot Guide](telegram-signals-bot.md).
+Runs as a stateless CronJob — no persistent connection. Downstream, `telegramsignalsbankbot` reads the stored messages and acts on signals. See [Telegram Signals Bot Guide](telegram-signals-bot.md).
 
 ---
 

docs/guides/telegram-signals-bot.md

@@ -1,6 +1,6 @@
 # Telegram Signals Bot Guide
 
-`telegram_signalsbankbot` is a trading bot that reads AI-summarized Telegram messages from the database, classifies them as BUY/SELL entry signals, and executes trades automatically.
+`telegramsignalsbankbot` is a trading bot that reads AI-summarized Telegram messages from the database, classifies them as BUY/SELL entry signals, and executes trades automatically.
 
 It is the **downstream consumer** of the `telegram-monitor` CronJob — the monitor fills the `telegram_messages` table, the signals bot acts on it.
 
@@ -62,7 +62,7 @@ The AI resolves broker-specific CFD names (US500, DJ30.c, XAUUSD) to Yahoo Finan
 ## Configuration
 
 ```python
-# telegram_signalsbankbot.py
+# telegramsignalsbankbot.py
 CHANNEL_ID = "-1001998690333"   # The Signals Bank - FREE
 LOOKBACK_DAYS = 3               # Only look at messages from last N days
 POSITION_SIZE_PCT = 0.2         # 20% of cash per signal
@@ -77,7 +77,7 @@ To monitor a different channel, change `CHANNEL_ID` to the numeric Telegram chan
 In `helm/tradingbots/values.yaml`:
 
 ```yaml
-- name: telegram_signalsbankbot
+- name: telegramsignalsbankbot
   schedule: "*/5 * * * *"  # Every 5 minutes — matches telegram-monitor cadence
 ```
 
@@ -91,7 +91,7 @@ No special env vars beyond the standard set — it reads from the same `postgres
 
 | File | Purpose |
 |---|---|
-| `tradingbot/telegram_signalsbankbot.py` | Bot implementation |
+| `tradingbot/telegramsignalsbankbot.py` | Bot implementation |
 | `tradingbot/utils/db.py` | `TelegramMessage` model (incl. `acted_on`) |
 | `helm/tradingbots/values.yaml` | Schedule configuration |
 

helm/tradingbots/values.yaml

@@ -181,7 +181,7 @@ bots:
   - name: taregimebot
     schedule: "20 17 * * 4"  # weekly 5:20 PM, Thursday
 
-  - name: telegram_signalsbankbot
+  - name: telegramsignalsbankbot
     schedule: "*/5 * * * *"  # Every 5 minutes (matches telegram-monitor cadence)
 
 # telegram monitor