explain formatted_release_note_from_excel

Author: qiancai

scripts/release-notes-generator-readme.md

@@ -182,7 +182,7 @@ This separation is intentional. If the same issue appears again in the same majo
 For target version `8.5.7`, the same-series quarantine sheet is named:
 
 ```text
-issues_already_in_earlier_v8.5_notes
+issue_already_in_earlier_v8.5.x
 ```
 
 A row is moved to this sheet when all of the following are true:

scripts/release_notes_ai/excel_workbook.py

@@ -372,7 +372,7 @@ def same_series_release_files_by_issue_url(
 
 def same_series_issues_sheet_name(version: str) -> str:
     major, minor, _patch = parse_semver_tuple(version)
-    return f"issues_already_in_earlier_v{major}.{minor}_notes"
+    return f"issue_already_in_earlier_v{major}.{minor}"
 
 
 def same_series_issue_reason(

scripts/release_notes_ai/prompts/generation.md

@@ -33,6 +33,12 @@ Contributors:
 Row context:
 {{ROW_CONTEXT}}
 
+About `formatted_release_note_from_excel`:
+
+- This field can be empty, `None`, or a generic placeholder such as `Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.`. In these cases, treat it as no usable release-note draft.
+- This field can also contain a draft release note written by the code PR author. In that case, use the draft as an important reference for the final release note, but verify and refine it against the PR code changes first and the issue description second.
+- Do not copy the draft blindly. Preserve its useful user-facing intent, correct unclear or inaccurate wording, and still follow all release-note style rules above.
+
 Improvements reference:
 {{IMPROVEMENTS_REFERENCE}}