文档补充：复核套件逐项写清（双盲复算、反方审稿、审批质询、数字推演沙盘、运行对比），新增「查询区间里没有数据」一节，补全访问密钥到期提醒发到哪里；中英文同步

- evidence.md「复核套件」：开头讲三项共用的只读核查 agent 和「设置 → 偏好设置 → 核查」，再按代码模块文档逐项写解决什么、怎么用、结果、局限；可验证报告的细节并进「导出」一节（只证明内部一致、封存后追加的单列、遮罩、何时能导出），复核套件里链过去
- evidence.md 新增「查询区间里没有数据」：整列是 0 时现查表里实际的日期范围，口径卡标「区间内无数据」、出具降档、写作提醒、问数据按复核重来、助手自查、宁可漏报；data-catalog.md 的数据剖析一节链过去
- schedules.md：访问密钥到期提醒写明个人密钥发本人的个人渠道、服务账号的密钥发全局渠道，以及消息里有什么；定时运行结束后的自动对比链到运行对比
- README 两版：功能列表加复核套件一条，文档索引里证据与出具一行补上新加的两节

scripts/check-docs.py：英文文档中文字符 0 处，相对链接 383 条全通，中英文档 18 对标题层级一致

docs/en/data-catalog.md

@@ -121,6 +121,7 @@ Profiling runs read-only queries to check the catalog's inferences and fill in s
 - The "Checked key count" profiling setting: `DISTINCT … LIMIT` doesn't take a random sample.
 - On MySQL / MariaDB, profiling notes for text columns state the collation, ENUM columns gain the values that don't appear in the data, and date columns state how many invalid dates were excluded.
 - The table list has a Profiling column, and the table details show the last profiling result.
+- The date ranges profiling records aren't reliable for tables fully reloaded every day, so whether the queried range has data is checked live at run time; the ranges recorded by profiling and value observation serve only as a fallback when the live check fails (see [No data in the queried range](evidence.md#no-data-in-the-queried-range)).
 
 By default, it profiles only "tables that need profiling": those never profiled, not finished last time, or that have since gained relationships awaiting verification or new code-value or date columns. On the same data source, drafting and profiling queue up one after the other, and the scope is set from the catalog as it stands when profiling starts, so you can click profile right after drafting finishes.