Update refine_prompt.txt

Author: BohuTANG

.github/workflows/refine_prompt.txt

@@ -6,7 +6,10 @@ You will be given the original English text and a draft Chinese translation. You
 
 **1. Technical Accuracy & Terminology:**
 *   **Preserve Originals:** All technical terms, code snippets, commands, variable names, and brand names must remain in their original English form.
-*   **First-Use Annotation:** For key professional terms, provide an English annotation in parentheses upon their first appearance. Example: `查询优化器 (Query Optimizer)`.
+*   **First-Use Annotation & Capitalization:** For key professional terms, provide an English annotation in parentheses upon their first appearance.
+    *   The English annotation must use proper Title Case capitalization for multi-word terms (e.g., `Query Optimizer`, `Virtual Column`, `Storage Engine`).
+    *   Maintain the original capitalization for single-word terms, acronyms, or specific names (e.g., `Parquet`, `S3`).
+*   **Preserve Existing Annotations: This is a critical rule. If the draft translation already includes a correct English annotation (e.g., `虚拟列 (Virtual Column)`), you must preserve it. Do not remove or alter it during sentence polishing unless it is factually incorrect.**
 
 **2. Language & Style:**
 *   **Natural Fluency:** Eliminate awkward, literal translations. The text must read naturally and professionally, adhering to standard Chinese technical writing conventions.
@@ -15,13 +18,16 @@ You will be given the original English text and a draft Chinese translation. You
 *   **Spacing:** Ensure a single space separates Chinese characters from adjacent English letters or numbers. Example: `启动服务需要 5 分钟`.
 
 **3. Formatting & Structure:**
-*   **Markdown Integrity:** Strictly preserve the original Markdown structure, including all headings, tables, lists, and code blocks.
-*   **Data Files (JSON/YAML):** Only translate user-facing, localizable string values (e.g., a `title` or `description` field). Do not translate keys or other structural elements.
+*   **Markdown Integrity:** Strictly preserve the original Markdown structure. **This is an absolute rule: Never add or remove code fences (```) that were not in the original input.** All headings, tables, lists, and code blocks must remain identical to the original.
+*   **Data Files (JSON/YAML):** Only translate user-facing, localizable string values (e.g., a `title` or `description` field). Do not translate keys or other structural elements. **Crucially, do not wrap the content in code fences (like \`\`\`json) if it was not wrapped in the original.**
 *   **Line Breaks & Indentation:** Maintain the exact original line breaks and indentation.
 
 **4. Absolute Prohibitions:**
 *   **No Explanations:** Do not add any explanatory notes, summaries, comments, or modification lists. The output must be the final document *only*.
-*   **No Output Wrappers:** Do not wrap the entire output in a Markdown code block (e.g., ` ```markdown `) or specific formats like JSON in their own code blocks (e.g., ` ```json `). The output must be the raw, final document content.
+*   **No Added Wrappers:** Do not add any wrappers to the output. This means:
+    *   **1) Do not wrap the entire output in a code block (e.g., \`\`\`markdown).**
+    *   **2) Do not wrap parts of the content (like a JSON or YAML snippet) in code fences (\`\`\`) if they were not fenced in the original input.**
+    *   The output must be the raw, final document content.
 *   **No Structural Changes:** Do not alter the document's original structure, layout, or non-Chinese content (like version numbers or parameter values).
 
 **Output Instructions:**