docs: align reader-digest-flow with async resume flow

reader-digest-flow/references/flow.md

@@ -34,6 +34,8 @@ Concrete operational checklist for the `reader-digest-flow` skill.
 - Generate two views from the same payload: a public digest for Hugo and an internal review digest for chat/operator workflow.
 - Do not expose internal review states or operator-facing labels in the public digest.
 - Do not re-fetch original URLs for selected summaries; use existing extracted text.
+- If the main pipeline fails, inspect the run first; when `inspect_resume_plan` says `recommended_action=resume`, continue via the async resume job path instead of stopping immediately.
+- Always branch on reader's top-level reconciled `status`; treat `status_source` and `state_conflict` only as explanatory metadata.
 - Prefer `ARTICLE_SUMMARY_*` for selected article summarization, with fallback to main `LLM_*` only if needed.
 - Actively report progress after each completed phase.
 
@@ -51,6 +53,17 @@ Formal production startup sequence:
 3. `get_freshrss_pipeline_job_result`
 4. after success, continue with `run_id` via `get_run_status` / `get_delivery_payload` / `get_run_report`
 
+If the main pipeline job ends in `failed`:
+
+1. inspect the linked run with `get_run_status`
+2. call `inspect_resume_plan(run_id)`
+3. if `recommended_action=resume`, continue with:
+   - `start_resume_job`
+   - `get_resume_job_status`
+   - `get_resume_job_result`
+4. if `recommended_action=read_terminal_result`, continue from the terminal run result
+5. if `recommended_action=start_new_run`, stop and report the failure
+
 Treat the old synchronous `run_freshrss_openclaw_pipeline` as debug / light validation / fallback only.
 
 Project root:
@@ -206,6 +219,12 @@ Expected inputs:
 - optional `output_dir`
 - optional article-summary LLM overrides
 
+Single-item rule:
+
+- when `extracted_path` is `outputs/freshrss/rerun/<run-id>/extracted/item-XX.extracted.json`, call one summary job per file
+- in that case, `selected_ids` should contain only the matching single `item_id`
+- if the candidate ID came from the delivery payload, strip the `cand:` prefix before passing it
+
 Recommended output layout:
 
 - `outputs/freshrss/single_summaries/YYYY-MM-DD/`
@@ -232,7 +251,7 @@ CLI fallback:
 ```bash
 python scripts/run_article_summaries.py \
   --extracted outputs/freshrss/rerun/<run-id>/extracted/item-01.extracted.json \
-  --ids <item_id_1> <item_id_2> \
+  --ids <item_id_without_cand_prefix> \
   --output-dir outputs/freshrss/single_summaries/YYYY-MM-DD
 ```