docs: consolidate product PR workflow and draft update article

Keep feature inventory, user-focused prioritization, draft confirmation,
article templates, screenshot guidance and publication checks in one guide.
Use separate new-feature, improvement and bug-fix sections, with explicit
image, replacement and verification markers in drafts.

Archive the unreleased update article and its evidence review, retaining
pending screenshots and release details. Remove the split guide files and
update release-runbook references.

Validation: documentation structure, draft markers, 59 local links and
anchors, and staged whitespace checks passed. No product code changed;
product tests and builds were not run.

docs/development/release-runbook.md

@@ -15,12 +15,12 @@ below.
 Product publicity is an optional companion to a release, not a release blocker
 or a replacement for the approved bilingual release notes. When requested,
 follow the [PR article workflow](../pr-articles/README.md) and choose either the
-[featured article](../pr-articles/featured-template.md) or
-[regular update](../pr-articles/regular-template.md) template based on user value,
+[featured article](../pr-articles/README.md#重点稿模板) or
+[regular update](../pr-articles/README.md#常规与综合稿模板) template based on user value,
 not version size or commit count.
 
 Prepare the draft and real screenshots against the candidate commit using the
-[isolated screenshot procedure](../pr-articles/screenshot-guide.md). This does
+[isolated screenshot procedure](../pr-articles/README.md#截图执行步骤). This does
 not waive the build, packaging, or launch restrictions below. Keep missing
 materials in the article's review record without delaying the software release.
 Before external publication, verify the final version, download links, upgrade