@nguyenphp/antigravity-marketing 1.0.18 → 1.0.19

package/templates/.agent/skills/minimax-docx/references/scenario_c_apply_template.md

@@ -0,0 +1,456 @@
+# Scenario C: Applying Formatting / Templates
+
+## When to Use
+
+Use Scenario C when:
+- The user has an existing document and wants to apply a different visual style
+- The user wants to rebrand a document (new fonts, colors, heading styles)
+- The user provides a template DOCX and wants its look applied to a content document
+- The user wants consistent formatting across multiple documents
+
+Do NOT use when: the user wants to edit content (→ Scenario B) or create from scratch (→ Scenario A).
+
+---
+
+## Workflow
+
+```
+1. Analyze source    → CLI: analyze source.docx      (list styles, fonts, structure)
+2. Analyze template  → CLI: analyze template.docx     (list styles, fonts, structure)
+3. Map styles        → Create mapping plan (source style → template style)
+4. Apply template    → CLI: apply-template source.docx --template template.docx --output result.docx
+5. Validate (XSD)    → CLI: validate result.docx --xsd wml-subset.xsd
+6. GATE-CHECK        → CLI: validate result.docx --xsd business-rules.xsd   ← MUST PASS
+7. Diff verify       → CLI: diff source.docx result.docx --text-only   (content must be identical)
+```
+
+---
+
+## What Gets Copied from Template
+
+| Part | File | Description |
+|------|------|-------------|
+| Styles | `word/styles.xml` | All style definitions (paragraph, character, table, numbering) |
+| Theme | `word/theme/theme1.xml` | Color scheme, font scheme, format scheme |
+| Numbering | `word/numbering.xml` | List and numbering definitions |
+| Headers | `word/header*.xml` | Header content and formatting |
+| Footers | `word/footer*.xml` | Footer content and formatting |
+| Section props | `w:sectPr` | Margins, page size, orientation, columns |
+
+## What Does NOT Get Copied
+
+| Part | Reason |
+|------|--------|
+| Document content | Paragraphs, tables, images stay from source |
+| Comments | Belong to source document's review history |
+| Tracked changes | Belong to source document's revision history |
+| Custom XML parts | Application-specific data, not visual |
+| Document properties | Title, author, dates belong to source |
+| Glossary document | Template's building blocks are not transferred |
+
+---
+
+## Template Structure Analysis (REQUIRED)
+
+Before choosing Overlay or Base-Replace, you MUST analyze the template's internal structure. This is the #1 cause of failure when skipped.
+
+### Step 1: Count template paragraphs and identify structural zones
+
+Run `$CLI analyze --input template.docx` or manually inspect:
+
+```bash
+# Quick structure scan
+scripts/docx_preview.sh template.docx
+```
+
+Identify these zones in the template:
+```
+Zone A: Front matter (cover page, declaration, abstract, TOC)
+        → These are KEPT from template, never replaced
+Zone B: Example/placeholder body content ("第1章 XXX", sample paragraphs)
+        → This is REPLACED with user's actual content
+Zone C: Back matter (appendices, acknowledgments, blank pages)
+        → These are KEPT from template or removed
+Zone D: Final sectPr
+        → ALWAYS kept from template
+```
+
+### Step 2: Find Zone B boundaries (replacement range)
+
+Search the template's document.xml for anchor text that marks the start and end of example content:
+
+**Start anchor patterns** (first paragraph of example body):
+- "第1章", "第一章", "Chapter 1", "1 Introduction", "绪论"
+- The first paragraph with a Heading1-equivalent style after TOC
+
+**End anchor patterns** (last paragraph before back matter):
+- "参考文献", "References", "致谢", "Acknowledgments"
+- The last paragraph before appendices or final sectPr
+
+```python
+# Pseudocode for finding replacement range
+for i, element in enumerate(template_body_elements):
+    text = get_text(element)
+    style = get_style(element)
+    if style in heading1_styles and ("第1章" in text or "Chapter 1" in text):
+        replace_start = i
+    if "参考文献" in text or "References" in text:
+        replace_end = i
+        break
+```
+
+**CRITICAL**: Verify the range by printing what's inside:
+```
+Template elements [0..replace_start-1]: front matter (KEEP)
+Template elements [replace_start..replace_end]: example content (REPLACE)
+Template elements [replace_end+1..end]: back matter (KEEP)
+```
+
+If replace_start or replace_end cannot be found, DO NOT proceed. Ask the user to identify the replacement boundaries.
+
+### Step 3: Decide Overlay vs Base-Replace
+
+Now that you know the structure:
+
+| Observation | Decision |
+|-------------|----------|
+| Template has ≤30 paragraphs, no cover/TOC | **C-1: Overlay** (pure style template) |
+| Template has >100 paragraphs with cover/TOC/example sections | **C-2: Base-Replace** |
+| Template paragraph count ≈ user document | **C-1: Overlay** (similar structure) |
+| Template paragraph count >> user document (e.g., 263 vs 134) | **C-2: Base-Replace** |
+
+### Step 4: For Base-Replace, execute the replacement
+
+1. Load template as base (all files)
+2. Extract user content elements using `list(body)` — NOT `findall('w:p')` (which misses tables)
+3. Build new body: `template[0:replace_start] + cleaned_user_content + template[replace_end+1:]`
+4. Apply style mapping to every paragraph
+5. Clean direct formatting (see rules below)
+6. Rebuild document.xml, keeping template's namespace declarations
+7. Merge relationships (images + hyperlinks)
+8. Write output using template as ZIP base
+
+---
+
+## Style Mapping Strategy
+
+When template style names differ from source style names, a mapping is required. **This step is mandatory** — skipping it is the #1 cause of formatting failures in template application.
+
+### Step 0: Extract StyleIds from Both Documents (REQUIRED)
+
+Before any template application, extract and compare styleIds from both documents:
+
+```bash
+# Extract all styleIds from source
+$CLI analyze --input source.docx --styles-only
+# Output example:
+#   Heading1  (paragraph, basedOn: Normal)
+#   Heading2  (paragraph, basedOn: Normal)
+#   Normal    (paragraph)
+#   ListBullet (paragraph, basedOn: Normal)
+
+# Extract all styleIds from template
+$CLI analyze --input template.docx --styles-only
+# Output example:
+#   1         (paragraph, basedOn: a, name: "heading 1")
+#   2         (paragraph, basedOn: a, name: "heading 2")
+#   3         (paragraph, basedOn: a, name: "heading 3")
+#   a         (paragraph, name: "Normal")
+#   a0        (character, name: "Default Paragraph Font")
+```
+
+**Critical distinction**: `w:styleId` vs `w:name`:
+```xml
+<!-- styleId="1" but name="heading 1" -->
+<w:style w:type="paragraph" w:styleId="1">
+  <w:name w:val="heading 1"/>
+  <w:basedOn w:val="a"/>
+</w:style>
+```
+
+The `w:styleId` attribute is what `<w:pStyle w:val="..."/>` references. The `w:name` attribute is the human-readable display name. **They can be completely different.** Many CJK templates use numeric styleIds (`1`, `2`, `3`, `a`, `a0`) instead of English names.
+
+### Tier 1: Exact StyleId Match
+If source uses `Heading1` and template defines `Heading1` as a styleId, map directly. No action needed.
+
+### Tier 2: Name-Based Match
+If no exact styleId match, try matching by `w:name` attribute:
+- Source `Heading1` (name="heading 1") → Template styleId `1` (name="heading 1")
+- Match is case-insensitive on the name value
+
+Within the same type, also try matching by:
+- Built-in style ID (Word's internal ID, e.g., heading 1 = built-in ID 1)
+- Style type (paragraph → paragraph, character → character, table → table)
+
+### Tier 3: Manual Mapping
+For renamed or custom styles, provide an explicit mapping:
+
+```json
+{
+  "styleMap": {
+    "Heading1": "1",
+    "Heading2": "2",
+    "Heading3": "3",
+    "Heading4": "3",
+    "Normal": "a",
+    "BodyText": "a",
+    "ListBullet": "a",
+    "CompanyName": "Title",
+    "OldTableStyle": "TableGrid"
+  }
+}
+```
+
+### Common Non-Standard StyleId Patterns
+
+| Template Origin | StyleId Pattern | Example |
+|----------------|-----------------|---------|
+| Chinese Word (default) | Numeric/alphabetic | `1`, `2`, `3`, `a`, `a0` |
+| English Word (default) | English names | `Heading1`, `Normal`, `Title` |
+| Google Docs export | Prefixed | `Subtitle`, `NormalWeb` |
+| WPS Office | Mixed | `1`, `Heading1`, custom names |
+| Academic templates | Custom | `ThesisHeading1`, `ThesisBody` |
+
+### Building the Mapping Table
+
+Follow this algorithm:
+
+1. **List source styleIds** actually used in `document.xml` (not all defined in `styles.xml`):
+   ```python
+   # Pseudocode: find all unique pStyle values in source document.xml
+   used_styles = set()
+   for p in body.iter('w:p'):
+       pStyle = p.find('w:pPr/w:pStyle')
+       if pStyle is not None:
+           used_styles.add(pStyle.get('val'))
+   ```
+
+2. **For each used style**, find the best match in template:
+   - First try: exact styleId match
+   - Second try: match by `w:name` value (case-insensitive)
+   - Third try: match by style purpose (any heading → template's heading style)
+   - Fallback: map to template's default paragraph style (usually `Normal` or `a`)
+
+3. **Validate the mapping** — every source styleId must map to an existing template styleId:
+   ```
+   ✓ Heading1 → 1 (name match: "heading 1")
+   ✓ Heading2 → 2 (name match: "heading 2")
+   ✓ Normal   → a (name match: "Normal")
+   ✗ CustomCallout → ??? (no match found, will fallback to 'a')
+   ```
+
+4. **Apply the mapping** when copying content — update every `<w:pStyle w:val="..."/>`:
+   ```xml
+   <!-- Source -->
+   <w:pPr><w:pStyle w:val="Heading1"/></w:pPr>
+   <!-- After mapping -->
+   <w:pPr><w:pStyle w:val="1"/></w:pPr>
+   ```
+
+### Unmapped Styles
+Styles in the source document that have no match in the template are logged as warnings:
+```
+WARNING: Style 'CustomCallout' has no mapping in template. Content will fall back to 'a' (Normal).
+```
+
+The content is preserved; only the style reference is updated to the template's default paragraph style.
+
+### C-2 BASE-REPLACE: Additional StyleId Considerations
+
+When using the template as a base document (C-2 strategy), the template's `styles.xml` is already in place. You must:
+
+1. **Never copy source `styles.xml`** — the template's styles are the authority
+2. **Map every content paragraph's pStyle** to the template's styleId before insertion
+3. **Strip direct formatting selectively** (see detailed rules below) — let the template style control appearance
+4. **Verify table styles** — if source tables use `TableGrid` but template defines it as `a3` or similar, remap `<w:tblStyle>` too
+5. **Check character styles** — `rPr` inside runs may reference character styles like `Hyperlink` or `Strong` that have different IDs in the template
+
+### Direct Formatting Cleanup Rules (Detailed)
+
+When copying content from source to template, apply these rules to EACH paragraph and run:
+
+**REMOVE from `<w:rPr>`:**
+- `<w:rFonts w:ascii="..." w:hAnsi="..."/>` — Latin font overrides (EXCEPT: keep `w:eastAsia`)
+- `<w:sz>`, `<w:szCs>` — font size (let style control)
+- `<w:color>` — text color
+- `<w:highlight>` — highlight color
+- `<w:shd>` — shading
+- `<w:b>`, `<w:i>` — bold/italic UNLESS the source style requires it (e.g., emphasis)
+- `<w:u>` — underline
+- `<w:spacing>` — character spacing
+
+**KEEP in `<w:rPr>`:**
+- `<w:rFonts w:eastAsia="宋体"/>` — CJK font declaration (MUST keep, or Chinese text renders wrong)
+- `<w:rFonts w:eastAsia="华文中宋"/>` — same reason
+- Anything inside `<w:drawing>` — image references (handle separately via rId remapping)
+
+**REMOVE from `<w:pPr>`:**
+- `<w:pBdr>` — paragraph borders
+- `<w:shd>` — paragraph shading
+- `<w:spacing>` — line/paragraph spacing (let style control)
+- `<w:jc>` — justification (let style control)
+- `<w:tabs>` — custom tab stops
+- `<w:rPr>` inside pPr — default run formatting for the paragraph
+
+**KEEP in `<w:pPr>`:**
+- `<w:pStyle>` — style reference (after mapping to template's styleId)
+- `<w:sectPr>` — section properties (if intentionally inserting section breaks)
+- `<w:numPr>` — numbering reference (after mapping numId to template's numbering)
+
+**Table cells (`<w:tc>`):**
+Apply the same rPr/pPr cleanup to every paragraph inside every cell. Also:
+- Keep `<w:tcPr>` structural properties (column span, row span, width)
+- Remove `<w:tcPr><w:shd>` (cell shading — let table style control)
+
+---
+
+## Relationship ID Remapping
+
+When copying parts (headers, footers, images) from the template into the source package, relationship IDs (`r:id`) may collide.
+
+**Problem**:
+- Source has `rId7` → `image1.png`
+- Template has `rId7` → `header1.xml`
+- Copying template's `rId7` overwrites source's image reference
+
+**Solution**:
+1. Scan source's `document.xml.rels` for all existing `rId` values
+2. Find the maximum numeric ID (e.g., `rId12`)
+3. Remap all template relationship IDs starting from `rId13`
+4. Update all references in copied parts to use new IDs
+
+```xml
+<!-- Template original -->
+<Relationship Id="rId1" Type="...header" Target="header1.xml" />
+
+<!-- After remapping into source package -->
+<Relationship Id="rId13" Type="...header" Target="header1.xml" />
+
+<!-- Update sectPr reference -->
+<w:headerReference w:type="default" r:id="rId13" />
+```
+
+### Hyperlink Relationship Merging
+
+When the source document contains external hyperlinks (e.g., URLs in references or footnotes), these are stored as relationships in `word/_rels/document.xml.rels`:
+
+```xml
+<Relationship Id="rId15" Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/hyperlink"
+              Target="https://example.com/paper" TargetMode="External"/>
+```
+
+The corresponding text in document.xml references this rId:
+```xml
+<w:hyperlink r:id="rId15">
+  <w:r><w:t>https://example.com/paper</w:t></w:r>
+</w:hyperlink>
+```
+
+**Merging steps:**
+1. Scan source document.xml for all `<w:hyperlink r:id="...">` elements
+2. For each, find the corresponding relationship in source's rels file
+3. Check if template already has a relationship with the same Target URL
+   - If yes: reuse the existing rId, update the hyperlink reference
+   - If no: assign a new rId (starting from template's max rId + 1), add the relationship to template's rels, update the hyperlink reference
+4. Also check for hyperlink relationships used in footnotes (`word/_rels/footnotes.xml.rels`) and endnotes
+
+**Common mistake:** Copying hyperlink paragraphs without merging rels → hyperlinks silently break (clicking does nothing in Word).
+
+---
+
+## XSD Gate-Check
+
+### What It Is
+
+After template application, the output document **MUST** pass `business-rules.xsd` validation. This is a **hard gate** — if it fails, the document is **NOT deliverable**.
+
+### What business-rules.xsd Checks
+
+| Rule | What It Validates |
+|------|-------------------|
+| Template styles exist | All styles referenced by content paragraphs are defined in `styles.xml` |
+| Margins match | Page margins match template specification |
+| Fonts correct | `w:docDefaults` fonts match template's font scheme |
+| Heading hierarchy | Heading levels are sequential (no H1 → H3 without H2) |
+| Required styles present | `Normal`, `Heading1`-`Heading3`, `TableGrid` exist |
+| Page size | Matches template's declared page size |
+
+### Handling Failures
+
+```
+GATE-CHECK FAILED:
+  - Style 'CustomStyle1' referenced in paragraph 14 but not defined in styles.xml
+  - Margin w:left=1080 does not match template requirement 1440
+```
+
+Fix each failure:
+1. **Missing style**: Add the style definition to `styles.xml`, or remap the paragraph to an existing style
+2. **Margin mismatch**: Update `w:sectPr` margins to match template
+3. **Font mismatch**: Update `w:docDefaults` to match template font scheme
+4. **Heading hierarchy gap**: Insert intermediate heading levels or adjust existing levels
+
+Re-validate after every fix until gate-check passes.
+
+---
+
+## Common Pitfalls
+
+### 1. Orphaned Numbering References
+
+**Problem**: Source document uses `w:numId="5"` in list paragraphs, but after replacing `numbering.xml` with the template's version, numbering ID 5 doesn't exist.
+
+**Symptom**: Lists appear as plain paragraphs (no bullets/numbers).
+
+**Fix**:
+- Map source numbering IDs to template numbering IDs
+- Update all `w:numId` references in document content
+- Or merge source numbering definitions into template's `numbering.xml`
+
+### 2. Missing Theme Colors
+
+**Problem**: Source document's styles reference theme colors (`w:themeColor="accent1"`) that have different values in the template's theme.
+
+**Symptom**: Colors change unexpectedly (usually acceptable — this IS the point of re-theming). But if a style uses `w:color` with both `w:val` and `w:themeColor`, the theme color wins in Word.
+
+**Fix**: Review color changes. If specific colors must be preserved, use explicit `w:val` without `w:themeColor`.
+
+### 3. Section Property Conflicts
+
+**Problem**: Source document has multiple sections (e.g., portrait + landscape pages), but the template assumes a single section.
+
+**Symptom**: All sections get the same margins/orientation, breaking landscape pages.
+
+**Fix**:
+- Only apply template section properties to the final `w:sectPr` in `w:body`
+- Preserve intermediate `w:sectPr` elements (inside `w:pPr`) from the source
+- Or apply template properties to all sections but preserve orientation overrides
+
+### 4. Embedded Font Conflicts
+
+**Problem**: Template specifies fonts not available on the target system.
+
+**Fix**: Either embed fonts in the DOCX (`word/fonts/`) or use web-safe alternatives:
+- Calibri → available on Windows/Mac/Office online
+- Arial → universal fallback
+- Times New Roman → universal serif fallback
+
+### 5. Broken Style Inheritance
+
+**Problem**: Template has `Heading1` based on `Normal`, but after applying template, `Normal` has different properties, cascading unwanted changes to headings.
+
+**Fix**: Verify the `w:basedOn` chain for all critical styles. Ensure base styles are also correctly transferred from template.
+
+---
+
+## Verification Checklist
+
+After template application, verify:
+
+1. **Content preserved** — text diff shows zero content changes
+2. **Gate-check passed** — `business-rules.xsd` validation succeeds
+3. **Styles applied** — headings, body text, tables use template formatting
+4. **Images intact** — all images render correctly (relationship IDs valid)
+5. **Lists working** — numbered and bulleted lists display correctly
+6. **Headers/footers** — template headers/footers appear on all pages
+7. **Page layout** — margins, page size, orientation match template
+8. **No corruption** — file opens without errors in Word

package/templates/.agent/skills/minimax-docx/references/track_changes_guide.md

@@ -0,0 +1,200 @@
+# Track Changes Guide
+
+## Overview
+
+Track Changes in OpenXML uses revision markup elements to record insertions, deletions, and formatting changes. Each revision has a unique ID, author, and timestamp.
+
+---
+
+## Insertion: `<w:ins>`
+
+Wraps runs that were inserted during tracking:
+
+```xml
+<w:ins w:id="1" w:author="John Smith" w:date="2026-03-21T10:30:00Z">
+  <w:r>
+    <w:rPr>
+      <w:rFonts w:ascii="Calibri" w:hAnsi="Calibri" />
+      <w:sz w:val="22" />
+    </w:rPr>
+    <w:t>This text was inserted.</w:t>
+  </w:r>
+</w:ins>
+```
+
+- `w:id` — unique revision ID (integer, must be unique across document)
+- `w:author` — free text string identifying the author
+- `w:date` — ISO 8601 format with timezone: `YYYY-MM-DDTHH:MM:SSZ`
+- Content inside is normal runs (`w:r`) with optional formatting
+
+---
+
+## Deletion: `<w:del>`
+
+Wraps runs that were deleted during tracking:
+
+```xml
+<w:del w:id="2" w:author="John Smith" w:date="2026-03-21T10:31:00Z">
+  <w:r>
+    <w:rPr>
+      <w:rFonts w:ascii="Calibri" w:hAnsi="Calibri" />
+      <w:sz w:val="22" />
+    </w:rPr>
+    <w:delText xml:space="preserve">This text was deleted.</w:delText>
+  </w:r>
+</w:del>
+```
+
+**CRITICAL**: Inside `<w:del>`, text MUST use `<w:delText>`, NOT `<w:t>`. Using `<w:t>` inside a deletion is invalid and will cause corruption or unexpected behavior. Word may silently repair it, but other consumers will fail.
+
+---
+
+## Formatting Change: `<w:rPrChange>`
+
+Records that a run's formatting was changed. Placed inside `w:rPr`, it stores the **previous** formatting:
+
+```xml
+<w:r>
+  <w:rPr>
+    <w:b />  <!-- Current: bold -->
+    <w:rPrChange w:id="3" w:author="Jane Doe" w:date="2026-03-21T11:00:00Z">
+      <w:rPr>
+        <!-- Previous: not bold (empty rPr means no formatting) -->
+      </w:rPr>
+    </w:rPrChange>
+  </w:rPr>
+  <w:t>This text was made bold.</w:t>
+</w:r>
+```
+
+The outer `w:rPr` holds the **new** (current) formatting. The `w:rPrChange` child holds the **old** (previous) formatting.
+
+---
+
+## Paragraph Property Change: `<w:pPrChange>`
+
+Records paragraph-level formatting changes (alignment, spacing, style):
+
+```xml
+<w:pPr>
+  <w:jc w:val="center" />  <!-- Current: centered -->
+  <w:pPrChange w:id="4" w:author="Jane Doe" w:date="2026-03-21T11:05:00Z">
+    <w:pPr>
+      <w:jc w:val="left" />  <!-- Previous: left-aligned -->
+    </w:pPr>
+  </w:pPrChange>
+</w:pPr>
+```
+
+---
+
+## Revision ID Management
+
+- Every revision element (`w:ins`, `w:del`, `w:rPrChange`, `w:pPrChange`, `w:tblPrChange`, etc.) requires a `w:id` attribute
+- IDs must be **unique integers** across the entire document
+- IDs should be **monotonically increasing** (not strictly required, but expected by Word)
+- When adding revisions, scan for the current maximum `w:id` and increment from there
+
+```
+Existing max ID: 47
+New insertion: w:id="48"
+New deletion: w:id="49"
+```
+
+---
+
+## Author and Date
+
+- **Author**: Free text. Use consistent strings (e.g., `"MiniMaxAI"` for all automated edits)
+- **Date**: ISO 8601 with UTC timezone marker: `2026-03-21T10:30:00Z`
+  - Must include the `T` separator and `Z` suffix (or `+HH:MM` offset)
+  - Omitting the date is allowed but not recommended
+
+---
+
+## Operations
+
+### Propose Insertion
+
+Add `<w:ins>` wrapper around new content at the target location:
+
+```xml
+<w:p>
+  <w:r><w:t>Existing text. </w:t></w:r>
+  <w:ins w:id="5" w:author="MiniMaxAI" w:date="2026-03-21T12:00:00Z">
+    <w:r><w:t>Proposed new text. </w:t></w:r>
+  </w:ins>
+  <w:r><w:t>More existing text.</w:t></w:r>
+</w:p>
+```
+
+### Propose Deletion
+
+Wrap existing content in `<w:del>` and change `<w:t>` to `<w:delText>`:
+
+```xml
+<w:p>
+  <w:r><w:t>Keep this. </w:t></w:r>
+  <w:del w:id="6" w:author="MiniMaxAI" w:date="2026-03-21T12:01:00Z">
+    <w:r>
+      <w:rPr><w:b /></w:rPr>
+      <w:delText>Remove this.</w:delText>
+    </w:r>
+  </w:del>
+  <w:r><w:t> Keep this too.</w:t></w:r>
+</w:p>
+```
+
+### Accept a Tracked Change
+
+- **Accept insertion**: Remove the `<w:ins>` wrapper, keep the inner runs as normal content
+- **Accept deletion**: Remove the entire `<w:del>` element and its content
+
+### Reject a Tracked Change
+
+- **Reject insertion**: Remove the entire `<w:ins>` element and its content
+- **Reject deletion**: Remove the `<w:del>` wrapper, change `<w:delText>` back to `<w:t>`
+
+---
+
+## Cross-Paragraph Operations
+
+### Deleting a Paragraph Break (Merging Paragraphs)
+
+When tracked deletion spans a paragraph boundary, use `<w:pPrChange>` on the merged paragraph:
+
+```xml
+<w:p>
+  <w:pPr>
+    <w:pPrChange w:id="7" w:author="MiniMaxAI" w:date="2026-03-21T12:05:00Z">
+      <w:pPr>
+        <w:pStyle w:val="Normal" />
+      </w:pPr>
+    </w:pPrChange>
+  </w:pPr>
+  <w:r><w:t>First paragraph text. </w:t></w:r>
+  <w:del w:id="8" w:author="MiniMaxAI" w:date="2026-03-21T12:05:00Z">
+    <w:r><w:delText> </w:delText></w:r>
+  </w:del>
+  <w:r><w:t>Second paragraph text (now merged).</w:t></w:r>
+</w:p>
+```
+
+### Inserting a New Paragraph
+
+The entire new paragraph is wrapped in `<w:ins>`:
+
+```xml
+<w:p>
+  <w:pPr>
+    <w:rPr>
+      <w:ins w:id="9" w:author="MiniMaxAI" w:date="2026-03-21T12:10:00Z" />
+    </w:rPr>
+  </w:pPr>
+  <w:ins w:id="10" w:author="MiniMaxAI" w:date="2026-03-21T12:10:00Z">
+    <w:r><w:t>Entirely new paragraph.</w:t></w:r>
+  </w:ins>
+</w:p>
+```
+
+The paragraph mark itself is marked as inserted via `w:ins` inside `w:pPr > w:rPr`.