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: