docs: harden digest SOP for hugo and IMA upload

reader-digest-flow/SKILL.md

@@ -128,11 +128,21 @@ Internal review digest writing rules:
 
 ### Phase 3: Publish to Hugo
 
-Publish only the public digest to Hugo and verify:
+Publish only the public digest to Hugo.
 
-- list page works
-- detail page works
-- latest digest is visible
+Required execution steps:
+
+1. write the public digest markdown to:
+   - `/home/ubuntu/zhu/apps/hugo-site/content/daily/YYYY-MM-DD/index.md`
+2. immediately redeploy Hugo:
+   - `cd /home/ubuntu/zhu/apps/hugo-site && ./redeploy.sh`
+3. verify before moving on:
+   - homepage works
+   - list page works
+   - detail page works
+   - latest digest is visible
+
+Do not treat “markdown file written” as equivalent to publish success. Hugo publish for this SOP is complete only after redeploy and page verification pass.
 
 Do not block on style polish unless the user explicitly asks.
 
@@ -169,6 +179,8 @@ Upload only the generated single-article markdown summaries to IMA.
 
 **Hard gate before upload:** even if the markdown file was generated by `reader`, do **not** upload it to IMA as-is. You must first reformat/check it against the IMA-facing Markdown rules in this skill, then upload the formatted version. Treat `reader` output as article-summary source material, not automatically as final IMA-ready Markdown.
 
+**Hard naming rule before upload:** the final uploaded Markdown filename must use the article's user-facing natural title (normally the original Chinese article title) plus `.md`. Do **not** use internal workflow names, slugs, prefixes, or temp filenames such as `ima-*`, `item-*`, `summary-*`, or English-only shorthand as the final IMA object name.
+
 Default target knowledge base for this phase:
 
 - `daily`
@@ -180,6 +192,7 @@ Completion criteria for this phase:
 
 - a selected article has been summarized from extracted content
 - a single-article Markdown summary file has been generated
+- the final upload filename has been normalized to a user-facing article title (not an internal slug / temp name)
 - the Markdown file is uploaded directly into the target knowledge base as a Markdown knowledge item (`media_type=7`)
 - the uploaded object preserves source link context and uses IMA-friendly layout for readability
 - the upload target is the `daily` knowledge base unless the user explicitly requests otherwise
@@ -204,6 +217,8 @@ IMA Markdown layout guidance for selected article deposition:
 - Remove stiff metadata headers such as `Source:` / `Category:` when preparing the IMA-facing Markdown.
 - Keep source traceability by placing `原文链接：` near the top, followed by the original URL on the next line.
 - Break long prose under `核心结论` and `主要论点` into short paragraphs for IMA readability instead of relying on platform auto-formatting.
+- The final upload filename should normally be `<文章标题>.md`; only when a same-name file already exists should you append a timestamp suffix before `.md`.
+- If local working files use internal slugs or prefixes for convenience, create or rename a final upload copy before calling IMA upload APIs.
 - Use `references/ima-markdown-example.md` as the formatting example whenever preparing the final upload file.
 - Completion for IMA upload requires both: (1) upload API success, and (2) the uploaded markdown having passed the above format checks.