docs: scope the move-detection warning to WmlComparer; strengthen a test

The warning told every caller to pair detect_moves with simplify_move_markup,
but docxdiff honours the former and rejects the latter, so a docxdiff user
following the docs hit a ValueError with no available mitigation. Scope the
warning and say what docxdiff does instead -- without claiming it is free of
the Word bug, which is untested.

test_docxodus_explicit_wmlcomparer_matches_default now parses and compares the
two revision counts rather than asserting each contains "9" independently, so
the test checks the equivalence its name promises.

Author: JSv4

README.md

@@ -136,7 +136,7 @@ redline_bytes, stdout, stderr = engine.run_redline(
 | `conflate_spaces` | bool | True | Treat breaking/non-breaking spaces the same |
 | `date_time` | str | now | Custom ISO 8601 timestamp for revisions |
 
-> **Warning:** Move detection can cause Word to display "unreadable content" warnings due to a known
+> **Warning:** (WmlComparer only) Move detection can cause Word to display "unreadable content" warnings due to a known
 > ID collision bug. When using `detect_moves=True`, always set `simplify_move_markup=True` as well.
 > This converts move markup to regular del/ins (loses green move styling but ensures Word compatibility).
 
@@ -159,6 +159,12 @@ engine.run_redline("Reviewer", original, modified, engine="docxdiff")
 rather than silently ignoring them. It does honour `detect_moves`, `case_insensitive`,
 `conflate_spaces`, `move_similarity_threshold`, `move_minimum_word_count`, and `date_time`.
 
+Move markup differs between the two. `docxdiff` renders moves natively and rejects
+`simplify_move_markup`, so the Word-compatibility mitigation described in the warning above is
+unavailable there; whether Word's ID-collision warning affects DocxDiff's native move markup is
+untested. If you need moves lowered to plain del/ins for maximum Word compatibility, use
+`engine="wmlcomparer"` with `simplify_move_markup=True`.
+
 ## Architecture Overview
 
 Both engines follow the same pattern: a Python wrapper class invokes a self-contained C# binary via subprocess.

tests/test_docxodus_engine.py

@@ -1,3 +1,5 @@
+import re
+
 import pytest
 
 from python_redlines.engines import DocxodusEngine
@@ -18,6 +20,13 @@ def modified_docx():
     return load_docx_bytes('tests/fixtures/modified.docx')
 
 
+def revision_count(stdout):
+    """The integer revision count from a Docxodus 'Redline complete: N revision(s) found' line."""
+    match = re.search(r"Redline complete: (\d+) revision\(s\) found", stdout)
+    assert match, f"no revision count in stdout: {stdout!r}"
+    return int(match.group(1))
+
+
 def test_run_docxodus_with_real_files(original_docx, modified_docx):
     wrapper = DocxodusEngine()
 
@@ -314,8 +323,10 @@ def test_docxodus_explicit_wmlcomparer_matches_default(original_docx, modified_d
     _, explicit_stdout, _ = engine.run_redline(
         "TestAuthor", original_docx, modified_docx, engine="wmlcomparer",
     )
-    assert "9 revision(s) found" in default_stdout
-    assert "9 revision(s) found" in explicit_stdout
+    default_count = revision_count(default_stdout)
+    explicit_count = revision_count(explicit_stdout)
+    assert explicit_count == default_count
+    assert default_count == 9
 
 
 def test_docxdiff_output_is_a_valid_docx_with_tracked_changes(original_docx, modified_docx):