docs: harden digest SOP for hugo and IMA upload

reader-digest-flow/references/flow.md

@@ -147,6 +147,17 @@ Internal review digest constraints:
 
 Publish only the public digest to Hugo.
 
+Hard execution steps:
+
+1. write the public digest markdown to:
+   - `/home/ubuntu/zhu/apps/hugo-site/content/daily/YYYY-MM-DD/index.md`
+2. redeploy Hugo immediately after writing:
+   - `cd /home/ubuntu/zhu/apps/hugo-site && ./redeploy.sh`
+3. verify all three URLs before continuing:
+   - `http://127.0.0.1:14322/`
+   - `http://127.0.0.1:14322/daily/`
+   - `http://127.0.0.1:14322/daily/YYYY-MM-DD/`
+
 Expected verification targets:
 
 - homepage works
@@ -189,6 +200,14 @@ python scripts/run_article_summaries.py \
 
 Upload only the generated markdown files for the selected articles.
 
+Hard execution rules before upload:
+
+1. reformat/check the generated markdown into IMA-facing final content
+2. normalize the final upload filename to `<文章标题>.md`
+3. do not use internal temp names such as `ima-*`, `item-*`, `summary-*`, or English slug filenames as the final uploaded object name
+4. if the knowledge base already contains the same filename, append a timestamp suffix before `.md`
+5. if local work needs internal temp names, create a final upload copy with the user-facing title before calling IMA APIs
+
 Default target knowledge base:
 
 - `daily`
@@ -204,3 +223,4 @@ Default target knowledge base:
 - Only explicitly user-selected articles go to IMA.
 - Selected article summaries use extracted text, not live refetch.
 - Prefer `ARTICLE_SUMMARY_*` for selected article summarization.
+- Final IMA upload filenames must use user-facing article titles, not internal slugs or workflow temp names.