docs: clarify openclaw handoff boundaries

docs/openclaw/openclaw-handoff.md

@@ -8,6 +8,22 @@ This repository provides a FreshRSS-first reading pipeline for OpenClaw:
 
 OpenClaw should treat this repository as an MCP-backed upstream content processor.
 
+This repository is responsible only for upstream reading-pipeline work:
+
+- FreshRSS pull
+- content extraction
+- LLM summary generation/validation
+- rule-based filtering
+- OpenClaw delivery payload generation
+- selected-article summary capability based on existing extracted text
+
+This repository should **not** take over downstream orchestration responsibilities that belong to OpenClaw / skills, such as:
+
+- Hugo publishing
+- chat reporting
+- user confirmation handling
+- IMA upload orchestration
+
 ## Production Entrypoint
 
 OpenClaw should call the MCP tool:
@@ -73,6 +89,7 @@ Recommended semantics:
 - Use `mark_read=false` only for debug, test, or validation runs.
 - Keep `debug_artifacts=false` for routine production runs.
 - Set `debug_artifacts=true` only when troubleshooting a bad batch.
+- If no real `openclaw-delivery-payload.json` was produced, OpenClaw should stop instead of generating a digest from placeholders or examples.
 
 ## What The Tool Returns
 
@@ -194,6 +211,15 @@ Recommended reading order for a new maintainer:
 6. `skills/keyword-cleanup-review/SKILL.md`
 7. `docs/current/context-reset-brief.md`
 
+## Downstream Boundary Rules
+
+For the daily-digest workflow:
+
+- the digest should go to Hugo and chat reporting, not directly into IMA
+- the full daily digest should **not** be uploaded to IMA
+- only explicitly user-selected article summaries should be uploaded to IMA
+- selected-article summaries should be generated from existing extracted text, not by re-fetching original URLs
+
 ## Current Recommendation
 
 For integration handoff, the repository is usable now.