fix: 强化 Hugo 公开版日报格式规则

- 编号强制使用 1. 2. 3.（禁止 ① ② ③ 等变体）
- 四个 section 缺一不可：今日概览/今日重点/趋势观察/延伸阅读
- Hugo 公开版必须包含 digest-brief.json 全部 keep 文章
- IMA 沉淀为下游独立步骤，不影响 Hugo 内容
- public-digest-example.md 顶部加格式警告注释

reader-digest-flow/references/flow.md

@@ -44,6 +44,15 @@ Concrete operational checklist for the `reader-digest-flow` skill.
 Use the formal MCP workflow path as the default production route.
 Prefer MCP run/status/result operations over direct path stitching. Only fall back to CLI or direct file inspection for debug / manual troubleshooting.
 
+Formal production startup sequence:
+
+1. `start_freshrss_pipeline_job`
+2. `get_freshrss_pipeline_job_status`
+3. `get_freshrss_pipeline_job_result`
+4. after success, continue with `run_id` via `get_run_status` / `get_delivery_payload` / `get_run_report`
+
+Treat the old synchronous `run_freshrss_openclaw_pipeline` as debug / light validation / fallback only.
+
 Project root:
 
 ```bash
@@ -130,6 +139,9 @@ Public digest constraints:
 - Optimize for concise public readability with solid information density.
 - For each `今日重点` item, add one short editor-style sentence explaining why the item matters in today's digest (for example: `这篇内容更值得关注的原因在于……`).
 - Prefer rendering highlight points as a short public label such as `值得关注：` followed by one bullet per line.
+- **Article numbering: MUST use `1.` `2.` `3.` (Arabic numeral + period). Do NOT use `① ② ③`，`一、二、三`，`第一条` or any other variant.**
+- **All four sections are required. Missing any one is a format violation.**
+- **Hugo digest must include ALL keep articles from `digest-brief.json`. The IMA deposition subset is a separate downstream step.**
 
 Recommended **internal review digest** structure:
 

reader-digest-flow/references/public-digest-example.md

@@ -4,6 +4,11 @@ date = 2026-04-01T16:55:00+08:00
 summary = "围绕 Agent 架构分层、Skills 标准化与桌面 Agent 工程实践的当日观察。"
 +++
 
+> ⚠️ 格式规范（生成 Hugo 时必须遵守）：
+> - 文章编号：`1.` `2.` `3.`（阿拉伯数字 + 点），禁止 `① ② ③` / `一、二、三` 等变体
+> - 四个 section 缺一不可：`今日概览` → `今日重点` → `趋势观察` → `延伸阅读`
+> - 每篇文章结构：标题来源 → 摘要段 → "值得关注："三点 → "这篇更值得关注的理由"段
+
 # 今日概览
 
 今天的公开候选主要集中在 AI Agent 的架构演进、工具化落地与工程化实践三条线索上。相比早期偏概念展示的讨论，这一批内容更强调模块化能力栈、真实部署路径与系统可维护性，说明行业关注点正在从“模型能做什么”转向“系统如何稳定落地并持续复用”。