# Cron Job: crash-auto-diagnose

**Job ID:** fd5d8aa41300
**Run Time:** 2026-10-30 08:01:27
**Schedule:** 0 8 * * *

**Prompt Characters:** 4210
## Prompt

[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. [SILENT] is a literal ASCII control token — never translate or rephrase it, whatever language the rest of your answer uses. Never combine [SILENT] with content — either report your findings normally, or say [SILENT] and nothing more. FAILURE: If a delegated child fails and this cron run must be recorded as failed, put [CRON_FAILURE] on the first line by itself, then explain the child failure on following lines. RECURSION: This is a run of an EXISTING scheduled job — execute the task now. NEVER create or update a cron job because of recurring or future-schedule language in the task prompt below; treat phrasing like "each Monday" or "every day at 9" as context for this run, not as a request to schedule another job.]

## Output from job 'edb0a7f09bc2'
The following is the most recent output from a preceding cron job. Use it as context for your analysis.

```
# Cron Job: 数据底座六源探测-每日3:40（P1-4）

**Job ID:** edb0a7f09bc2
**Run Time:** 2026-10-30 03:42:20
**Mode:** no_agent (script)

---

wind       edb                  ❌      0.1s  search failed: unknown

✅ 已保存: capability_matrix.json（81 项能力）
✅ 已保存: capability_details.json（全详情，供 hub.get_capability_probe() 查询）
矩阵: {"MX": ["realtime", "daily", "finance", "news", "us", "fund", "board", "select", "stock_select", "zixuan_query", "moni_assets"], "mootdx": [], "tushare": ["daily", "weekly", "monthly", "daily_basic", "fina_indicator", "income", "stk_limit", "top10_holders", "index_daily", "stock_basic", "trade_cal", "adj_factor", "margin", "ths_index", "block_trade", "stock_company", "lhb", "macro", "forecast", "express", "concept", "ths_daily", "ths_member", "index_classify", "tdx_index"], "westock": ["cli_mark

📊 因果基因（脚本自证）
- 数据源: 四主源mootdx/tushare/mx/westock + 补充源gf_skills/ifind 全方法探测（probe_sources.py --save）
- 分析路径: 逐源逐方法探测可用性 → 回显探测摘要 → 刷新data/capability_matrix.json能力掩码供自动路由
- 判断: rc=0=能力矩阵已更新；rc非0=输出[ALERT]探测失败并以1退出，交看门狗归因
```

## Output from job '8da391caf5a0'
The following is the most recent output from a preceding cron job. Use it as context for your analysis.

```
# Cron Job: 每日独立市场扫描-06:45

**Job ID:** 8da391caf5a0
**Run Time:** 2026-10-30 06:46:04
**Mode:** no_agent (script)

---

数据完整度: 3/3 段可用

📡 独立市场扫描 · 10/30 06:45

🌍 海外
韩国综合指数(KS11.GI)(指数)  →  -1.244%  →  -  →  -
纳斯达克(IXIC.GI)(指数)  →  -1.375%  →  -  →  -
日经225(N225.GI)(指数)  →  1.103%  →  -  →  -
台湾加权(TWII.GI)(指数)  →  -1.419%  →  -  →  -
恒生指数(HSI.HI)(指数)  →  -0.5897%  →  142.8亿手  →  1895亿港元

📊 大盘
指数  →  收盘  →  涨跌幅%  →  成交额(亿)
上证指数  →  3651.43  →  -0.82  →  71,562
沪深300  →  4041.84  →  -1.03  →  41,189
科创50  →  1228.09  →  -4.27  →  7,110
  （数据日 20261029）
  （源: tushare — 非交易时段按老板令换源，本段不调用 mx）

📂 板块
板块  →  点位  →  涨跌幅%
半导体  →  12752.07  →  -5.54
创新药  →  1165.52  →  -1.87
银行  →  1430.67  →  +1.98
保险  →  8198.89  →  +1.65
航天装备  →  2865.48  →  +1.73
通信设备  →  1541.87  →  -8.09
  （数据日 20261029；同花顺指数名未匹配: 光纤光缆）
  （源: tushare — 非交易时段按老板令换源，本段不调用 mx）

📊 因果基因（脚本自证）
- 数据源: 海外段=妙想 mx_data.py（tushare index_global 不覆盖韩/纳指）；大盘+板块段=tushare(mx_daily_scan_tushare.py index_daily / ths_index+ths_daily)——2026-10-13 老板令「mx 实时数据只在交易时段用，非交易时段换 tushare，海外除外」，本 cron 06:45 属非交易时段故换源
- 分析路径: 三段取数 → clean_table规整 → 「数据完整度 N/3」头 + 分段输出
- 判断: 海外/大盘/板块涨跌成交额概览；缺失段显式降级解读，全失败不发空壳
```

你是崩溃自动诊断agent。读取最近生成的crash report，诊断根因，尝试修复。

步骤：
1. 用 `ls -t ~/.hermes/crash_reports/ | head -5` 看今天有没有新报告，只处理【最新 1 份】
2. 今天没有新的crash report → 回复[SILENT]，不打扰用户
3. 读报告只取关键字段：时间、脚本名、退出码、"错误日志"段的最后 20 行（按需 tail 截取）；
   不整份复制，不把大段原始日志、进程表、环境变量搬进对话
4. 分析处理：
   a. 崩溃根因是什么（超时被终止、依赖缺失、路径/权限、数据源限流、数据为空）
   b. 是否可以自动修复（文件权限、路径错误、依赖缺失、超时预算）→ 有明确把握才动手
   c. 不能修复的 → 给出人工处理建议
   d. 修复后跑一遍原命令验证，附命令与退出码
5. 查历史crash report（同名脚本），判断是否重复出现
6. 输出 ≤3 行：根因 / 已修或人工建议 / 验证结果

注意：
- 只修复有明确把握的问题，不确定的不修
- 同一错误3天内出现3次 → 标记为系统性问题，必须人工处理
- 输出纪律：只写结论和命令+退出码；不粘贴原始日志全文，不读取、不引用、不回显任何密钥/token/密码/连接串/配置文件内容（需要时用占位符）；用中性工程措辞描述故障

**Response Characters:** 8
## Response

[SILENT]