refactor: rename telegram_qa to telegram_assistant

Author: Yili-code

.github/workflows/telegram_qa.yml .github/workflows/telegram_assistant.yml.github/workflows/telegram_qa.yml renamed to .github/workflows/telegram_assistant.yml

@@ -47,4 +47,4 @@ jobs:
           TELEGRAM_CHAT_ID: ${{ secrets.TELEGRAM_CHAT_ID }}
           GEMINI_API_KEY: ${{ secrets.GEMINI_API_KEY }}
           GEMINI_MODEL: ${{ vars.GEMINI_MODEL }}
-        run: python src/telegram_qa.py
+        run: python src/telegram_assistant.py

docs/README.en.md

@@ -53,7 +53,7 @@ This is a GitHub Actions-driven automation project for tracking and filtering Ji
 - Keyword filtering with built-in defaults and optional `KEYWORDS_FILE`
 - Gemini grading and summary logic: `src/gemini.py`
 - Telegram push messaging: `src/tg01.py`
-- Telegram Q&A listener: `src/telegram_qa.py`
+- Telegram Q&A listener: `src/telegram_assistant.py`
 - Shared recent-news context: `data/recent_news.json`
 - Scheduled execution via GitHub Actions every 6 hours
 
@@ -74,10 +74,10 @@ Telegram push
    ↓
 Save to data/recent_news.json
    ↓
-telegram_qa.py answers questions using recent context
+telegram_assistant.py answers questions using recent context
 ```
 
-`jin10_monitor.py` and `telegram_qa.py` run as separate processes and share the same `recent_news.json` file for context.
+`jin10_monitor.py` and `telegram_assistant.py` run as separate processes and share the same `recent_news.json` file for context.
 
 ---
 
@@ -116,7 +116,7 @@ python src/jin10_monitor.py
 ### 5. Run the Telegram Q&A bot (optional)
 
 ```bash
-python src/telegram_qa.py
+python src/telegram_assistant.py
 ```
 
 In a Telegram group, you can mention the bot or use `/ask`; in private chat, you can send a question directly.
@@ -130,7 +130,7 @@ This project includes two workflows:
 | Workflow | Purpose |
 |---|---|
 | `flash_monitor.yml` | Runs `src/jin10_monitor.py` on a schedule and pushes filtered news |
-| `telegram_qa.yml` | Runs `src/telegram_qa.py` to answer Telegram questions |
+| `telegram_assistant.yml` | Runs `src/telegram_assistant.py` to answer Telegram questions |
 
 Set these in GitHub `Settings → Secrets and variables → Actions`:
 

docs/README.md

@@ -53,7 +53,7 @@
 - 關鍵字過濾：支援內建關鍵字清單，也可用 `KEYWORDS_FILE` 自訂
 - Gemini 分級與摘要：`src/gemini.py`
 - Telegram 推播：`src/tg01.py`
-- Telegram 對話問答：`src/telegram_qa.py`
+- Telegram 對話問答：`src/telegram_assistant.py`
 - 共享近期新聞上下文：`data/recent_news.json`
 - GitHub Actions 自動執行：每 6 小時排程一次，支援手動觸發
 
@@ -74,10 +74,10 @@ Telegram 推播
    ↓
 寫入 data/recent_news.json
    ↓
-telegram_qa.py 依背景資料回答 Telegram 問題
+telegram_assistant.py 依背景資料回答 Telegram 問題
 ```
 
-`jin10_monitor.py` 和 `telegram_qa.py` 是兩個獨立流程，共同使用 `recent_news.json` 作為近期快訊上下文。
+`jin10_monitor.py` 和 `telegram_assistant.py` 是兩個獨立流程，共同使用 `recent_news.json` 作為近期快訊上下文。
 
 ---
 
@@ -116,7 +116,7 @@ python src/jin10_monitor.py
 ### 5. 啟動 Telegram 問答腳本（可選）
 
 ```bash
-python src/telegram_qa.py
+python src/telegram_assistant.py
 ```
 
 在群組中可直接 @ 機器人或使用 `/ask`；私人聊天則可直接輸入問題。
@@ -130,7 +130,7 @@ python src/telegram_qa.py
 | Workflow | 作用 |
 |---|---|
 | `flash_monitor.yml` | 執行 `src/jin10_monitor.py`，監控快訊並推播 |
-| `telegram_qa.yml` | 執行 `src/telegram_qa.py`，接收 Telegram 問題並回答 |
+| `telegram_assistant.yml` | 執行 `src/telegram_assistant.py`，接收 Telegram 問題並回答 |
 
 在 GitHub 的 `Settings → Secrets and variables → Actions` 中新增：
 

src/jin10_monitor.py

@@ -316,7 +316,7 @@ async def summarize_with_gemini(session: aiohttp.ClientSession, text: str) -> Op
     }
 
 
-# ─── Recent flash context (for telegram_qa.py Q&A) ───────────────────────────
+# ─── Recent flash context (for telegram_assistant.py Q&A) ───────────────────────────
 
 recent_news: deque[dict] = deque(maxlen=CONTEXT_MAX_ITEMS)
 

src/telegram_qa.py src/telegram_assistant.pysrc/telegram_qa.py renamed to src/telegram_assistant.py

@@ -90,12 +90,12 @@ def extract_question(text: str, bot_username: str, chat_type: str) -> Optional[s
 
 # ─── Main loop ─────────────────────────────────────────────────────────────────
 
-async def telegram_qa_loop(session: aiohttp.ClientSession) -> None:
+async def telegram_assistant_loop(session: aiohttp.ClientSession) -> None:
     bot_username = await get_bot_username(session)
     if bot_username:
-        log.info("Telegram Q&A listener started. Bot username: @%s", bot_username)
+        log.info("Telegram Assistant listener started. Bot username: @%s", bot_username)
     else:
-        log.info("Telegram Q&A listener started (bot username not available; in groups, use the /ask command)")
+        log.info("Telegram Assistant listener started (bot username not available; in groups, use the /ask command)")
 
     url = f"{TELEGRAM_API}/getUpdates"
     offset: Optional[int] = None
@@ -150,7 +150,7 @@ async def main() -> None:
         log.warning("GEMINI_API_KEY is not set; Q&A will always return a failure message")
 
     async with aiohttp.ClientSession() as session:
-        await telegram_qa_loop(session)
+        await telegram_assistant_loop(session)
 
 
 if __name__ == "__main__":

src/test_telegram_listener.py

@@ -12,7 +12,7 @@
 
 GITHUB_TOKEN = os.getenv("GITHUB_TOKEN", "")
 GITHUB_REPOSITORY = os.getenv("GITHUB_REPOSITORY", "")
-GITHUB_WORKFLOW_FILE = os.getenv("GITHUB_WORKFLOW_FILE", "telegram_qa.yml")
+GITHUB_WORKFLOW_FILE = os.getenv("GITHUB_WORKFLOW_FILE", "telegram_assistant.yml")
 
 
 async def check_webhook(session: aiohttp.ClientSession) -> None:
@@ -59,7 +59,7 @@ async def check_polling_conflict(session: aiohttp.ClientSession) -> None:
     if resp.status == 409:
         print(f"❌ 409 Conflict: {body.get('description', '')}")
         print("    Another process is currently polling getUpdates.")
-        print("    Check: local telegram_qa.py instance or running GitHub Actions job.")
+        print("    Check: local telegram_assistant.py instance or running GitHub Actions job.")
     elif resp.status == 200:
         print("✅ No conflict detected at this moment.")
         print("Note: This is a point-in-time check; run multiple times for intermittent issues.")