fix(reader-digest-flow): enforce IMA markdown pre-upload checks

reader-digest-flow/SKILL.md

@@ -165,6 +165,8 @@ Use the real extracted JSON structure already produced by the project. Do not in
 
 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.
+
 Default target knowledge base for this phase:
 
 - `daily`
@@ -195,9 +197,13 @@ Do not upload:
 IMA Markdown layout guidance for selected article deposition:
 
 - Prefer direct Markdown file upload into the knowledge base (`media_type=7`).
+- Before every upload, open and check the actual markdown file that will be uploaded; do not assume the generator already matched IMA style.
+- The upload target must be an IMA-facing formatted markdown file, not the raw default output from `reader` if the styles differ.
 - 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.
+- 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.
 
 ## Operational Guidance