docs: polish digest output workflow rules

reader-digest-flow/SKILL.md

@@ -56,7 +56,13 @@ Produce two output views from the same run, preferably in **one generation step*
 1. **Public digest** — for Hugo / public browsing
 2. **Internal review digest** — for chat reporting and operator decisions
 
-Write only the public digest into Hugo using this structure:
+Before publishing, persist digest outputs back into the same reader run directory under:
+
+- `outputs/freshrss/rerun/<run-id>/digest/public_digest.md`
+- `outputs/freshrss/rerun/<run-id>/digest/internal_review_digest.md`
+- `outputs/freshrss/rerun/<run-id>/digest/combined.json`
+
+Then write only the public digest into Hugo using this structure:
 
 - `content/daily/YYYY-MM-DD/index.md`
 
@@ -69,7 +75,6 @@ Recommended **public digest** structure:
 - `今日重点`
 - `趋势观察`
 - `延伸阅读`
-- `信息来源`
 
 Public digest writing rules:
 
@@ -79,6 +84,7 @@ Public digest writing rules:
 - Do **not** expose internal workflow labels or operator language such as `待确认`, `建议沉淀到 IMA`, `keep/review/drop`, or `selection_decision`.
 - Prefer concise but information-dense writing.
 - For each item under `今日重点`, include not only summary and highlights, but also one short editor-style value sentence, for example: `这篇内容更值得关注的原因在于……`.
+- When rendering highlights in public digest, prefer a short label such as `值得关注：` followed by one item per line, instead of packing multiple points into a single long sentence.
 
 Recommended **internal review digest** structure: