wooo/ewoooc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
326 Commits 6 Branches 0 Tags
b5a2b09445bebbcc5d4bb78a391e28c543ac28a5
Commit Graph

326 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
OoO
b5a2b09445 fix(ppt): matplotlib CJK fallback covers container Noto CJK JP variant
All checks were successful
CD Pipeline / deploy (push) Successful in 2m19s
Details 
實戰驗證在 188 容器內發現：matplotlib font_manager 從 fonts-noto-cjk
ttc 檔只載入 'Noto Sans CJK JP' / 'Noto Serif CJK JP' 兩個變體（TC/SC/HK/KR
名稱未列入 ttflist），導致原本 fallback 清單比對失敗 → font.family 退到
'sans-serif'（DejaVu Sans）→ 中文 glyph 全部缺失印出 UserWarning。

修正：
- _mpl_setup() fallback 清單加入 'Noto Sans CJK JP' / 'Noto Serif CJK JP'
- 最終 fallback 加 substring match（涵蓋未列入但名稱含 CJK/PingFang/
  JhengHei/YaHei/Source Han/WenQuanYi/Hiragino 的字型）
- _mpl_horiz_bar_png 內重複的 cjk_candidates 邏輯移除，改呼叫 _mpl_setup
  避免兩處清單漂移

註：Noto Sans CJK JP ttc 檔本身含完整 CJK Unified Ideographs，可正常
渲染中文（漢字共用），只是字型名稱叫 JP 而已。

bump 模板版本（舊圖表中文方塊版本快取應失效重生）：
- daily   v3.0   → v3.0.1
- weekly  v3.0   → v3.0.1
- monthly v3.1   → v3.1.1

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 23:38:51 +08:00
OoO
1c81866541 fix(ppt): final critic cleanup — Medium-1 OOXML order + Info-1/2 docs
All checks were successful
CD Pipeline / deploy (push) Successful in 2m29s
Details 
清掉剩餘 critic finding（Medium-1 + Info-1 + Info-2）：

Medium-1: _set_run_fonts 違反 OOXML CT_TextCharacterProperties 子元素順序
- 抽出 _insert_rpr_child(rPr, tag) helper：依 ECMA-376 §21.1.2.3 規定
  的順序表（_RPR_CHILD_ORDER）找正確位置插入
- 找第一個排在 target 之後的子元素 → insert 前面；否則 append
- 當前 from-scratch 場景安全；未來改讀模板 .pptx 時也不會踩雷
- 驗證：產生 monthly v3.1，399 個 rPr 全部符合 schema 順序，0 違反

Info-1: cleanup_expired_ppt_cache docstring 補語意說明
- 明確說明 dry_run=True/False 時 deleted_files / deleted_rows / freed_bytes
  欄位語意分別為「將刪除」預估值 vs「已實刪」實際值

Info-2: TEMPLATE_VERSIONS 標記退役 type
- growth / vendor / bcg 三個 type 從未實際落地（依 ADR-014 校正 2026-04-28）
- 加 DEPRECATED 註解，避免後人誤以為已支援

Info-3 SKIP（評估後不做）：
- get_template_version import 改放模組頂部會 trigger ppt_generator 模組級
  REPORTS_DIR.mkdir() 副作用，read-only filesystem 環境會掛
- 保留延遲 import 是 graceful degradation 的 intentional 設計

至此 critic 38967ce 審查清單全綠：
- 0 critical, 2 HIGH (3b0b4b3), 4 medium (52c06f6 + 本 commit), 3 info

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 17:39:27 +08:00
OoO
52c06f6861 fix(ppt): admin guard for destructive /cache commands (critic Medium-3)
All checks were successful
CD Pipeline / deploy (push) Successful in 2m14s
Details 
Critic Medium-3：群組內任意成員可執行破壞性快取指令的問題。

新增機制：
- ADMIN_USER_IDS：新增 OPENCLAW_ADMIN_USER_IDS 環境變數
  逗號分隔的 user_id；未設時退回 ALLOWED_USERS（向後兼容）
- _is_admin(user_id)：fail-closed 判定函式
- _CURRENT_USER_ID_CTX：ContextVar 在 webhook 入口（msg + callback）
  set 當前 user_id，避免改 handle_cmd 30+ 處呼叫端簽名

權限模型：
| 指令                              | 權限    | 行為                |
| /cache status                     | 已授權  | 任何已授權用戶可看  |
| /cache cleanup [days]             | 已授權  | 預設乾跑可預覽      |
| /cache flush <type>               | admin   | 拒絕非 admin        |
| /cache cleanup [days] confirm     | admin   | 拒絕非 admin        |
| /cache cleanup [days<1] confirm   | -       | 強制乾跑（防呆）    |

非 admin 嘗試破壞性指令時，回傳清楚錯誤訊息引導設定環境變數。
admin 操作會額外寫 sys_log.warning 留軌跡（含 user_id）。

煙霧測試：
- syntax OK
- _is_admin(None) / _is_admin("abc") / _is_admin(unknown_id) 皆 False
- ContextVar set/get 行為正確

剩餘 Medium 1/2 + Info 類後續再處理（非緊急）。

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 17:35:48 +08:00
OoO
3b0b4b3d42 fix(ppt): address critic findings on commit 38967ce (HIGH-1, HIGH-2, Medium-4)
All checks were successful
CD Pipeline / deploy (push) Successful in 2m27s
Details 
Critic 審查 38967ce 找出 2 HIGH + 4 medium，本 commit 修最緊急三項：

HIGH-2: cleanup_expired_ppt_cache 預設 dry_run=False 危險
- 函式 default 改 dry_run=True（呼叫方需明確傳 False 才實刪）
- launchd 排程腳本改用 DRY_RUN 環境變數，預設 false→實刪，
  但測試時可 DRY_RUN=true 安全跑
- /cache cleanup Telegram 指令預設乾跑，需加 confirm 才實刪
- /cache cleanup days<1 強制乾跑（防呆）

HIGH-1: matplotlib 三個 helper 缺 try/finally → 渲染失敗洩漏 figure
- _mpl_horiz_bar_png / _mpl_line_chart_png / _mpl_pareto_chart_png
  全部用 try/except/finally 包住，例外時 plt.close() 仍執行
- 同時讓渲染失敗回 None（呼叫端自然 fallback 到原生 chart）

Medium-4: scripts/ppt_cleanup.sh PROJECT_DIR 寫死
- 改用相對路徑解析（cd $SCRIPT_DIR/..），手動執行不再需要設環境變數
- VENV_PY 找不到時 fallback 到系統 python3（容器友善）
- 新增 DRY_RUN 環境變數開關（預設 false）

煙霧測試：
- syntax OK (services/ppt_generator.py + routes/openclaw_bot_routes.py)
- monthly v3.1 重生 10 頁 290KB
- cleanup_expired_ppt_cache dry_run default = True ✓

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 17:23:02 +08:00
OoO
38967ceea3 feat(ppt): redesign all 6 reports to professional standard + cache versioning
All checks were successful
CD Pipeline / deploy (push) Successful in 13m18s
Details 
PPT 模板全面升版至市場專業標準（McKinsey / BCG 月報級別）：

Monthly v3.1（10 頁）
- 暖紙感封面（去黑底）+ elevator pitch（亮點/警訊/動能徽章）
- KPI 卡含 △% vs 上月 + 紅綠燈、YoY 同期對比帶
- matplotlib 業績趨勢折線（本月+上月+日均線+高低點）
- 品類分析雙視圖：橫條 + 帕雷托累計（80% 主力線）
- TOP 50 商品（自動分頁）+ vs 上月 △ 排名變化 / 🆕 新進榜
- MCP 情報 4 卡片結構化、AI 行動結構化分區、附錄頁

Daily / Weekly / Strategy / Promo / Competitor v3.0
- 統一暖紙封面、AI 頁去黑底改暖紙 + 焦糖橘色條
- 日週改 matplotlib 折線（含日均線、高低點）
- 全部加附錄頁（資料來源 / 計算口徑 / 模板版本）

Cache 版本控制
- TEMPLATE_VERSIONS 字典自動注入 cache key (tpl_ver)
- 模板升版舊快取自動 miss → 重生
- 新增 _invalidate_ppt_cache() 與 cleanup_expired_ppt_cache() helper
- 新增 /cache status / flush / cleanup Telegram 指令

字型系統
- _set_run_fonts() 用 lxml 直寫 a:latin/a:ea，中英分軌
- 中文走 Microsoft JhengHei，數字/英文走 Consolas（點陣等寬）
- Dockerfile 加 fonts-noto-cjk + fonts-noto-cjk-extra

部署排程
- scripts/install_ppt_cleanup.sh 一鍵安裝 launchd（每日 03:15）
- scripts/ppt_cleanup.sh 清 7 天前過期 PPT 檔 + DB row

資料層
- routes monthly: query_monthly_summary LIMIT 10 → 50，補 orders 欄位
- routes monthly: 拉 prev_month / prev_year 比較資料供 KPI △ 與商品 △ 計算

煙霧測試 6/6 全綠：
- 日報 v3.0 (5 頁) / 週報 v3.0 (6 頁) / 月報 v3.1 (10 頁)
- 策略 v3.0 (6 頁) / 促銷 v3.0 (6 頁) / 競品 v3.0 (5 頁)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 16:26:27 +08:00
OoO
0232dbb902 test(openclaw): assert /menu returns full main menu keyboard 2026-05-02 16:13:43 +08:00
OoO
3f40089d8c fix(openclaw): show full main menu for wakeup phrases
All checks were successful
CD Pipeline / deploy (push) Successful in 2m44s
Details
2026-05-02 16:12:30 +08:00
OoO
7b6423fa67 fix(openclaw): route wakeup phrases back to menu
All checks were successful
CD Pipeline / deploy (push) Successful in 2m55s
Details
2026-05-02 16:03:49 +08:00
OoO
673982d83b Fix OpenClaw callback command path from NL dispatch regression
All checks were successful
CD Pipeline / deploy (push) Successful in 4m17s
Details
2026-05-02 15:59:54 +08:00
OoO
76304602b1 fix(ppt): footer→bottom, font spec (Courier New/Microsoft JhengHei), 50-item paginated table, remove old single-page remnant
All checks were successful
CD Pipeline / deploy (push) Successful in 2m41s
Details
2026-05-02 15:32:54 +08:00
OoO
0b82350745 style(ppt): comprehensive warm-tone redesign - caramel KPI cards, warm paper MCP/AI pages, revenue ratio bars in product table, chart→caramel orange, cover with warm decorative bands 2026-05-02 15:20:02 +08:00
OoO
ccc0cef9be feat(ppt): upgrade monthly AI prompt to 7-section expert template with MCP RAG integration, enrich data_summary with category/product breakdown
All checks were successful
CD Pipeline / deploy (push) Successful in 2m47s
Details
2026-05-02 15:06:16 +08:00
OoO
4c6e4ca5fb style(ppt): align PPT palette perfectly with MOMO Pro v2 design tokens (Beige, Warm Ink, Caramel Orange) as per frontend upgrade roadmap 2026-05-02 15:01:55 +08:00
OoO
934adc957c style(ppt): redesign ppt layouts, align palette with frontend, and add dedicated MCP RAG slide 2026-05-02 14:59:45 +08:00
OoO
9068d463bb feat(ea): execute Phase 3 C-series architecture fixes to prevent recurrence
All checks were successful
CD Pipeline / deploy (push) Successful in 2m37s
Details 
- C1: Removed weekly_strategy and meta_analysis from Elephant Alpha's SAFE_ACTIONS (orchestrator prompt and engine _ACTION_ZH) to prevent autonomous generation of scheduled reports
- C2: Removed hardcoded 0.85 confidence example from orchestrator prompt and implemented bounding validation (0.0~1.0) in _parse_strategic_decision
- C3: Expanded ADR-019 data freshness gate (_ppt_check_data_freshness) to cover /ppt weekly and /ppt strategy routes, proactively warning users of stale data
 2026-05-02 14:39:10 +08:00
OoO
9158bbe1a6 fix(ea): execute Phase 2 B-series data quality and gate improvements
All checks were successful
CD Pipeline / deploy (push) Successful in 2m40s
Details 
- B1 & B2: Updated SQL column names from 銷售金額 to 總業績 in openclaw_strategist_service.py and chart_generator_service.py
- B3: Removed bare except statements in DB fetchers to raise errors instead of failing silently
- B4: Implemented freshness gate (MAX(snapshot_date) < CURRENT_DATE - 2) in daily_sales_snapshot to prevent generating stale reports and send data stalled alerts
- B5: Replaced hardcoded 45.0 system load percentage with actual psutil CPU metric
 2026-05-02 14:34:30 +08:00
OoO
e6df2fad28 fix(ea): remove weekly_strategy/meta_analysis from autonomous engine triggers (Phase 1 stopgap)
All checks were successful
CD Pipeline / deploy (push) Successful in 2m39s
Details 
Critic-approved 3-point revision (REVISE → adopted):
1. Disable weekly_insight trigger at definition (line 279-285) — EA no
   longer evaluates the 6h / >=5 ai_insights condition that fired
   _generate_strategy_report without force_tg_alert=True.
2. Remove the openclaw weekly/meta dispatch table branches (line 591-606).
   The 5 actions (generate_strategic_analysis, generate_weekly_strategy,
   generate_market_analysis, generate_pricing_strategy,
   generate_meta_analysis) now fall through to the existing
   `raise ValueError(f"Unrecognized step: ...")` at line 631, which
   _execute_decision's try/except converts into a circuit-breaker failure.
   This is the correct failure semantics critic asked for.
3. Convert _generate_strategy_report / _generate_meta_report into hard
   RuntimeError raisers and drop their imports of
   openclaw_strategist_service. Deep insurance: any future caller crashes
   immediately instead of silently bypassing dedupe.

Evidence: ai_insights logged 35+ duplicate weekly_strategy sends in 7 days
because EA's `_generate_strategy_report` invoked
generate_weekly_strategy_report() without force_tg_alert=True, bypassing
the run_scheduler.py weekly dedupe gate.

Out of scope (per task contract):
- run_scheduler.py:115 Monday 06:00 schedule — preserved (sole owner)
- services/openclaw_strategist_service.py — owned by B-series (SQL)
- Other EA triggers (price_drop_alert / market_opportunity /
  threat_escalation / code_exception / resource_optimization) — preserved
- Other dispatch branches (hermes / nemotron / auto_heal / code_fix /
  price_adjustment review) — preserved
- Did NOT add force_tg_alert=True defensive layer (critic flagged as
  anti-pattern)
- Did NOT touch _TRIGGER_TO_DECISION_TYPE / _ALLOWED_ACTION_TYPES

Not pushed, not deployed. D1 deployment will be issued separately and
must use `docker compose up -d --no-deps --force-recreate momo-scheduler`
(per feedback_compose_restart_vs_up).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:12:14 +08:00
OoO
477aab3f6f refactor(telegram): migrate edm_notifier text path to EventRouter (ADR-019 Phase 5)
Some checks failed
CD Pipeline / deploy (push) Has been cancelled
Details 
services/edm_notifier.py 的 _send_telegram() 處理 EDM 媒體告警，原本 if/else
分流 sendPhoto / sendMessage。

行為變化：
- 純文字分支（無 image_path）：改走 services.event_router.dispatch_sync()
  event_type=edm_media_alert, severity=warning
- 含圖片分支（sendPhoto with multipart file upload）：依 ADR-019 任務指示
  保留直連 Telegram API（EventRouter 不支援 file upload，列為 known skip）
- caller 行為不變，失敗仍 logger.error 不阻斷主線

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:09:34 +08:00
OoO
3e9d53c98c refactor(telegram): migrate aider_heal_executor sender to EventRouter (ADR-019 Phase 5) 
services/aider_heal_executor.py 的 _notify_telegram() 為 ADR-013 AutoHeal 閉環
通知出口（aider 自動修復進度）。原直接 POST sendMessage，timeout=5s（非阻塞）。
改走 services.event_router.dispatch_sync()。

行為變化：
- 失敗仍靜默 pass，caller（execute_code_fix 等）行為完全不變
- severity=warning 會被 EventRouter classify 為 L0 或 L1（無 trace 時 L0），
  輕量分流不會拖慢自動修復流程
- 享 EventRouter 內建 retry + JSONL queue replay；舊版 timeout=5 失敗即丟訊息
  的問題改善（可從 queue 重送）

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:09:34 +08:00
OoO
84786be06f refactor(telegram): migrate cicd_routes sender to EventRouter (ADR-019 Phase 5) 
routes/cicd_routes.py 的 send_telegram_message() 用於 CI/CD pipeline 失敗 / Drone
build 異常等告警。原本直接 POST sendMessage，改走 services.event_router.
dispatch_sync()（event_type=cicd_pipeline_alert, severity=alert）。

行為變化：
- parse_mode 從 Markdown 改 HTML（EventRouter 統一）；既有訊息中的 *bold* 等
  Markdown 控制字元會以純文字顯示，可讀性不受顯著影響
- 失敗保留 print + return False 同舊行為，不阻斷 caller（send_pipeline_failure_alert
  等）的 try/except 結構

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:09:34 +08:00
OoO
ea78d0814b refactor(telegram): migrate alert_routes sender to EventRouter (ADR-019 Phase 5) 
routes/alert_routes.py 的 send_telegram_message() 是 Alertmanager webhook 通用告警
出口，原本直接 POST sendMessage 並對每個 chat_id 迴圈。改走 services.event_router.
dispatch_sync() 統一入口（event_type=alertmanager_webhook, severity=alert）。

行為變化：
- 移除手動 chat_id 迴圈，改傳 admin_chat_ids 給 EventRouter（內部仍逐一發）
- 新增 ADR-012 三層分流（L0/L1/L2）+ JSONL queue replay 失敗重送
- parse_mode 參數保留簽名向後相容，但實際統一走 EventRouter HTML 模板
- caller（Alertmanager webhook handler）的 try/except 結構未動

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:09:34 +08:00
OoO
edfe38e87d refactor(telegram): migrate nemoton_dispatcher sender to EventRouter (ADR-019 Phase 5) 
NemoTron Dispatcher 的 _send_telegram() 原本直接 POST Telegram Bot API（含 MarkdownV2
跳脫）+ 透過 self.nm 走 NotificationManager 兩條路。改為統一走 services.event_router.
dispatch_sync()，享 EventRouter 的 retry + 失敗 JSONL queue replay + AI 三層分流。

行為變化：
- 從 _exec_trigger_price_alert / _exec_add_to_recommendation / _exec_flag_for_human_review
  三個工具實作流入 EventRouter，event_type=nemoton_dispatch_alert，severity=alert
- 移除 self.nm._send_telegram_messages() 的 short-circuit；改由 EventRouter 內建
  通道處理 chat_ids/token 解析
- 失敗時保留 logger.error + log fallback，不阻斷主線（同舊行為）

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:09:34 +08:00
OoO
e12e6a8f96 feat(telegram): ADR-019 Phase 6 - daily data freshness probe + cron 09:05
Some checks failed
CD Pipeline / deploy (push) Has been cancelled
Details 
ADR-019 Phase 6：每日 09:05 OpenClawBot scheduler 主動巡檢 realtime_sales_monthly
最新資料日期，落後超過閾值時透過 EventRouter 發 Telegram 警告。

新增 services/data_freshness_probe.py：
- gap == 0：靜默不發（資料齊全）
- gap == 1：info（昨日資料齊，正常）
- gap == 2~3：warning
- gap >= 4：alert（P2，ETL 大概率出問題）
- latest_date 取不到：alert（DB 連線異常）

routes/openclaw_bot_routes.py 加 cron job openclaw_data_freshness_probe
（hour=9 minute=5，避開 09:00 的其他既有 job）。

從『用戶月初按按鈕踩坑才發現資料缺口』的被動模式，轉成 agent 主動巡檢通知。
配合 Phase 1（PPT freshness gate）+ Phase 2（agent tool）+ Phase 3（cmd 路徑
agent dispatch）+ Phase 4（對話 state），Telegram Bot 互動層的『rigid default
+ 靜默空白』反模式根除。

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:07:30 +08:00
OoO
14195b65fd feat(telegram): ADR-019 Phase 4 - conversation memory + chat_id propagation
All checks were successful
CD Pipeline / deploy (push) Successful in 2m51s
Details 
ADR-019 Phase 4：新增 services/openclaw_session.py 管理 chat_id 級別的多輪
對話歷史與 carry-over slot。In-memory，30 分鐘 TTL，重啟清空（臨時對話 state
不該污染 ai_insights 永久記憶）。

openclaw_answer 簽章加 chat_id=None 可選參數：
- 傳入時 agent 會看到該 chat 最近 5 輪對話歷史，注入 system prompt
- Ollama / Gemini FC 兩條路徑都會在生成成功後 append_turn 寫回 session
- system prompt 加決策規則：「若歷史顯示用戶剛被問參數，優先用該答案接續執行」

Caller 全部更新傳 chat_id：
- routes/openclaw_bot_routes.py:5479 (handle_cmd 不認識指令 fallback)
- routes/openclaw_bot_routes.py:5916 (webhook NL 路徑)
- routes/openclaw_bot_routes.py:_agent_dispatch_cmd (Phase 3 hook)
- services/telegram_bot_service.py:934 (polling NL fallback)

向下相容：chat_id=None 時行為與舊版完全相同（無 multi-turn 記憶）。

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:04:18 +08:00
OoO
38f4033eb0 feat(telegram): ADR-019 Phase 3 - feature-flagged agent dispatch for cmd:X
All checks were successful
CD Pipeline / deploy (push) Successful in 2m47s
Details 
ADR-019 Phase 3：在 handle_cmd 入口插入 agent dispatch hook，將白名單 cmd 翻成
NL question 交 OpenClaw agent 處理。Agent 自動透過 Phase 2 的 check_data_freshness
tool probe 資料缺口，缺資料時主動詢問用戶，避免靜默產出空白結果。

新增：
- 環境變數 OPENCLAW_AGENT_DISPATCH (預設 0)、OPENCLAW_AGENT_DISPATCH_CMDS (逗號分隔)
- _CMD_TO_NL 翻譯字典：sales / top / vendor 三 cmd 起步
- _agent_dispatch_cmd() helper：feature flag + 白名單 + agent 呼叫 + 失敗 fallback

設計考量：
- 預設 OFF，零 prod regression 風險
- Agent 失敗自動回原 handler，不卡用戶
- 灰度路徑：先在 staging 開 OPENCLAW_AGENT_DISPATCH=1 + CMDS=sales 觀察一週
- 21 cmd 不需要全部翻譯，只翻譯有「資料缺口可能性」或「參數需確認」的

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 13:00:02 +08:00
OoO
b3348ae77d feat(telegram): ADR-019 Phase 2 - check_data_freshness tool for OpenClaw
Some checks failed
CD Pipeline / deploy (push) Has been cancelled
Details 
ADR-019 Phase 2：把資料新鮮度查詢註冊為 OpenClaw 的第 4 個 Function Calling
tool。Agent 在回答任何特定時段業績問題前可主動 probe，避免月初/季初時編造
「業績為零」這類因 ETL 尚未匯入造成的虛假結論。

新增：
- _FC_TOOLS 加入 check_data_freshness 宣告
- _execute_tool 對應分支：回傳 latest_data_date / available_months /
  current_month_has_data / data_freshness_warning
- 系統 prompt 更新：明示 4 個工具與「相對時間詞先 probe」決策規則

與 Phase 1 互補：Phase 1 是 PPT cmd 路徑寫死的補丁，Phase 2 讓 NL 對話路徑
透過 agent 自己決策，是 ADR-019「Agent-First」原則的真正起點。

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 12:58:06 +08:00
OoO
db02ecf2cf feat(telegram): ADR-019 Phase 1 - PPT data freshness gate + store_insight fix
All checks were successful
CD Pipeline / deploy (push) Successful in 2m55s
Details 
ADR-019 Phase 1 (止血)：PPT 生成前 probe 資料新鮮度。月初/缺資料期間用戶按
ppt:monthly/daily 不再產出空白報告，改主動 inline keyboard 詢問：
  - 改看最新有資料的月份/日期（一鍵）
  - 自訂月份/日期（接 await:date_ppt_*）
  - 取消

新增 PPTDataInsufficientError exception + _ppt_check_data_freshness() helper。
_generate_ppt_cmd 簽章加 _reply_to=None；_ppt_background 靜默吞此例外。

順手修同檔 :1976/:1993 兩處 store_insight() positional args 錯位 bug —
原本 (date, report_type, ai_text) 對應 signature (insight_type, content, period)
完全錯位，導致 period varchar(50) 被 2000 字 AI 內容截斷、INSERT 失敗、
ai_insights 表寫入永久失敗。改成 kwargs 呼叫。

ADR-019 (Telegram Bot Agentic Conversation Layer) 同步落地，Status: Accepted。
六 Phase 路線圖見 ADR 文件，本 commit 完成 Phase 1。

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 12:52:45 +08:00
OoO
1a886d962b fix(telegram): dedupe webhook+polling updates via shared DB guard
All checks were successful
CD Pipeline / deploy (push) Successful in 8m50s
Details 
Webhook (Flask) and polling (momo-telegram-bot) consumed the same
Telegram update_id, causing /menu callbacks to fire twice. Add a
shared dedup module backed by telegram_update_dedup table (300s TTL,
60s cleanup) with in-memory fallback, wired into both paths.

Polling launcher now skips startup when webhook is configured to
prevent dual-consumption at the source.

38 tests across webhook, menu keyboards, telegram_api, dedup guard,
and trend bot service.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 12:01:04 +08:00
OoO
75de76ac12 fix(momo): block EC404 auto-open with end-to-end URL guard
Some checks failed
CD Pipeline / deploy (push) Has been cancelled
Details 
- normalize URLs at write time (scheduler crawlers, routes) to drop
  javascript:/EC404/placeholder i_code (momo_/manual_/pchome_)
- add global click+auxclick guard in base.html and ewoooc_base.html
  that intercepts blocked MOMO URLs and redirects to safe i_code URL
- per-page dashboards reuse the same isLikelyMomoIcode validation
- /api/track_momo_link records blocked events for diagnosis
- ship sanitize_momo_urls.py to clean existing polluted DB rows

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-02 12:00:34 +08:00
OoO
026d0e7539 feat(reports): move monthly analysis to v2 shell
All checks were successful
CD Pipeline / deploy (push) Successful in 2m14s
Details
2026-05-01 21:13:18 +08:00
OoO
d6782ee710 feat(ai): move recommendation page to v2 shell
All checks were successful
CD Pipeline / deploy (push) Successful in 2m13s
Details
2026-05-01 21:08:44 +08:00
OoO
9b3e0a4565 feat(ai): move history page to v2 shell
All checks were successful
CD Pipeline / deploy (push) Successful in 2m19s
Details
2026-05-01 21:06:17 +08:00
OoO
939ed5eef5 feat(ai): move intelligence page to v2 shell
All checks were successful
CD Pipeline / deploy (push) Successful in 2m18s
Details
2026-05-01 21:03:19 +08:00
OoO
7d46ff9ba5 feat(competitor): persist match attempts
All checks were successful
CD Pipeline / deploy (push) Successful in 2m9s
Details
2026-05-01 20:56:17 +08:00
OoO
c1f43b0ae4 fix(campaign): persist full crawl snapshots
All checks were successful
CD Pipeline / deploy (push) Successful in 2m22s
Details
2026-05-01 20:48:28 +08:00
OoO
bb99dfeab6 feat(campaign): restore operations table signals
Some checks failed
CD Pipeline / deploy (push) Has been cancelled
Details
2026-05-01 20:43:46 +08:00
OoO
4e853a233f perf(dashboard): speed up competitor overview
All checks were successful
CD Pipeline / deploy (push) Successful in 2m12s
Details
2026-05-01 20:36:25 +08:00
OoO
b9d6186d68 feat(frontend): sync latest MOMO Pro prototype styling
All checks were successful
CD Pipeline / deploy (push) Successful in 2m18s
Details
2026-05-01 20:32:23 +08:00
OoO
066cf1846f feat(dashboard): show AI pick evidence gaps
All checks were successful
CD Pipeline / deploy (push) Successful in 2m18s
Details
2026-05-01 17:17:03 +08:00
OoO
e86075d59d fix(dashboard): avoid redundant prewarm rebuilds
All checks were successful
CD Pipeline / deploy (push) Successful in 2m15s
Details
2026-05-01 16:36:58 +08:00
OoO
2ac7410d40 fix(dashboard): prewarm cache and expose pick evidence
All checks were successful
CD Pipeline / deploy (push) Successful in 2m20s
Details
2026-05-01 16:34:13 +08:00
OoO
9e2337764b fix(ai): supersede old product picks
All checks were successful
CD Pipeline / deploy (push) Successful in 2m48s
Details
2026-05-01 16:24:15 +08:00
OoO
b3d00a011c fix(dashboard): warm cache after AI pick refresh
All checks were successful
CD Pipeline / deploy (push) Successful in 3m37s
Details
2026-05-01 16:16:39 +08:00
OoO
b447aefcfb fix(ai): clear dashboard cache after pick regeneration
All checks were successful
CD Pipeline / deploy (push) Successful in 2m27s
Details
2026-05-01 16:10:51 +08:00
OoO
3920701e1a feat(dashboard): optimize cache and AI pick confidence
All checks were successful
CD Pipeline / deploy (push) Successful in 2m46s
Details
2026-05-01 16:01:52 +08:00
OoO
0334051aa7 feat(dashboard): 匯出 AI 挑品操作清單
All checks were successful
CD Pipeline / deploy (push) Successful in 2m39s
Details
2026-05-01 15:43:57 +08:00
OoO
1d1a7f6e94 feat(dashboard): 強化 AI 挑品清單決策資訊
All checks were successful
CD Pipeline / deploy (push) Successful in 2m22s
Details
2026-05-01 15:22:21 +08:00
OoO
a5de082437 feat(dashboard): 顯示 50 品 AI 挑品清單
All checks were successful
CD Pipeline / deploy (push) Successful in 3m12s
Details
2026-05-01 15:08:41 +08:00
OoO
6bce46bbc7 fix(runtime): 強化健康檢查監控韌性
All checks were successful
CD Pipeline / deploy (push) Successful in 2m29s
Details
2026-05-01 14:46:49 +08:00
OoO
77b085f813 fix(dashboard): 快取比價決策總覽
All checks were successful
CD Pipeline / deploy (push) Successful in 2m28s
Details
2026-05-01 14:32:51 +08:00