docs: align reader docs with digest SOP defaults

README.md

@@ -19,6 +19,13 @@ The server exposes five tools:
 
 Article-summary post-processing (separate LLM optional):
 
+**Recommended production input for selected-article summaries**
+
+- Use the per-item extracted files written by the main FreshRSS pipeline:
+  - `outputs/freshrss/rerun/<run_id>/extracted/item-XX.extracted.json`
+- Treat these per-item extracted files as the formal default artifacts for downstream selected-article summarization.
+- A batch extracted file such as `outputs/freshrss/extracted/freshrss.extracted.json` is only a compatible input shape for ad hoc or legacy workflows, not the preferred production default.
+
 Daily knowledge-base defaults:
 
 - `IMA_DAILY_KNOWLEDGE_BASE_ID` — default IMA knowledge base ID for daily single-article summaries
@@ -77,6 +84,8 @@ The script writes:
 - `outputs/freshrss/items/freshrss.items.json`
 - `outputs/freshrss/extracted/freshrss.extracted.json`
 
+Note: this batch extracted file is mainly a compatible artifact for standalone extraction runs and older workflows. The formal production default for downstream selected-article summarization is still the per-item extracted output under `outputs/freshrss/rerun/<run_id>/extracted/item-XX.extracted.json`.
+
 Run the full FreshRSS pipeline and mark items as read only after the final OpenClaw delivery payload is written:
 
 ```bash
@@ -248,7 +257,8 @@ set ARTICLE_SUMMARY_LLM_API_KEY=your-article-summary-key
 set ARTICLE_SUMMARY_LLM_MODEL=deepseek-chat
 ```
 
-Then run, for example, either via the CLI script:
+Then run, for example, either via the CLI script.
+For normal production use, prefer a per-item extracted file from `outputs/freshrss/rerun/<run_id>/extracted/`. The batch extracted example below is kept only as a compatible legacy/ad hoc input shape:
 
 ```bash
 python scripts/run_article_summaries.py ^