docrev 0.9.5 → 0.9.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docrev",
-  "version": "0.9.5",
+  "version": "0.9.7",
   "description": "Academic paper revision workflow: Word ↔ Markdown round-trips, DOI validation, reviewer comments",
   "type": "module",
   "types": "dist/lib/types.d.ts",

package/skill/REFERENCE.md

@@ -21,11 +21,38 @@ rev import manuscript.docx --output ./project
 ### rev sync
 Sync feedback from a reviewed Word document into existing markdown sections.
 ```bash
-rev sync reviewed.docx       # Updates markdown with track changes/comments
-rev sync                     # Auto-detect most recent .docx
+rev sync reviewed.docx          # Updates markdown with track changes/comments
+rev sync                        # Auto-detect most recent .docx
 rev sync reviewed.docx methods  # Sync only methods section
+rev sync reviewed.docx --comments-only  # Insert comments only; never modify prose
 ```
 
+`--comments-only` skips the Word→Markdown diff entirely. Use it when the
+markdown has been revised between sending the docx out for review and
+receiving it back: applying track changes from a stale draft would clobber
+newer edits, but comments still need to land. Comments are placed at
+fuzzy-matched anchors against the current prose. Pair with
+`rev verify-anchors` to see which ones won't fit before you run sync.
+
+### rev verify-anchors
+Report drift between Word comment anchors and the current markdown.
+```bash
+rev verify-anchors reviewed.docx       # Print per-comment match quality
+rev verify-anchors reviewed.docx --json  # Machine-readable report
+```
+
+Each comment is classified by how well its anchor still matches the current
+section prose:
+
+- `clean` – exact or whitespace-normalized hit
+- `drift` – anchor only matches via stripped-CriticMarkup or partial-prefix fallbacks
+- `context-only` – anchor text is gone, only surrounding context survives
+- `ambiguous` – multiple candidate positions; needs context to disambiguate
+- `unmatched` – nothing maps; user must place the comment manually
+
+Useful before `rev sync --comments-only` to plan which comments will land
+automatically and which need manual placement.
+
 ### rev build
 Build output documents from markdown sections.
 ```bash

package/skill/SKILL.md

@@ -44,10 +44,18 @@ Send to reviewers. They add comments and track changes in Word.
 ### 3. Import feedback
 
 ```bash
-rev sync reviewed.docx       # Updates markdown with annotations
-rev sync                     # Auto-detect most recent .docx
+rev sync reviewed.docx              # Updates markdown with annotations
+rev sync                            # Auto-detect most recent .docx
+rev sync reviewed.docx --comments-only  # Insert comments only; never modify prose
+rev verify-anchors reviewed.docx    # Report which anchors still match current prose
 ```
 
+Use `--comments-only` when the markdown has been revised between sending the
+docx out and receiving it back. Without the flag, track changes from a stale
+draft would clobber newer edits. With it, only comments are imported, placed
+at fuzzy-matched anchors against the current prose. Run `rev verify-anchors`
+first to see which comments will land cleanly and which need manual placement.
+
 ### 4. View and address comments
 
 ```bash
@@ -111,6 +119,8 @@ rev response                 # Generate point-by-point response letter
 | Create LaTeX project | `rev new my-project --template latex` |
 | Import Word doc | `rev import manuscript.docx` |
 | Sync Word feedback | `rev sync reviewed.docx` |
+| Sync comments only (prose unchanged) | `rev sync reviewed.docx --comments-only` |
+| Verify anchors against current prose | `rev verify-anchors reviewed.docx` |
 | Sync PDF comments | `rev sync annotated.pdf` |
 | Extract PDF comments | `rev pdf-comments annotated.pdf` |
 | Extract with highlighted text | `rev pdf-comments file.pdf --with-text` |