hermes-skills/skills/legal/contract-pass-workflow/references/manual-review-checklist-0713.md

Manual Review Checklist (2026-07-13 session)

When Doro asks to "审查workflow修改的情况" on delivered contracts, follow this checklist:

Process

1. Read the审查规则 first — full text of review-rules-root.md
2. Get both files: original from 待审查/ + delivered from 任务交付/
3. Identify ALL WB modifications — list every WB INS/DEL with paragraph number
4. Distinguish WB from original revisions — other authors (WB-1, 86187, etc.) are original, don't touch
5. Check each WB modification against rules — one by one
6. Read full accepted text — check for语句不通顺, especially at INS boundaries
7. Fix problems directly — don't ask Doro if you should fix. Just fix.
8. Report findings — list what's correct and what's wrong
9. Wait for Doro to say pass — never self-initiate pass

Common Workflow Issues Found (2026-07-13)

1. INS rFonts多余属性

Workflow consistently adds hAnsi, cs, hint to WB INS runs even when original runs only have eastAsia + ascii. Fix: strip these three attributes from all WB INS rPr/rFonts.

2. Sub-numbering not updated

When workflow inserts a new chapter (e.g. 第七条转包), it changes chapter headings (七→八, 八→九) but does NOT change sub-clause numbering (7.1→8.1, 8.1→9.1, 9.1→10.1). Fix: add DEL old number + INS new number for each sub-clause.

3. New clause heading format mismatch

• Wrong pStyle (e.g. Style15 instead of Heading4)
• Extra space in heading text (e.g. "第七条 转包" vs original "第六条违约责任" no space)
• Missing paragraph properties (spacing, ind) that originals have

4. Missing "法律顾问修订版" footer

Workflow sometimes doesn't add the footer. Fix: add via python-docx, then wrap the run in w:ins author=WB (must be tracked change format).

5. Duplicate content insertion

P32 example: original already had "保密义务不因合同解除...而免除", but WB added another "本条保密义务不因本合同的终止或解除而终止" — semantic duplicate. Fix: remove WB's duplicate.

6. Sentence flow at INS boundaries

WB appends保密/数据归属 text directly after original sentence without transition. If the original sentence's context doesn't naturally lead into the INS content (e.g. "遵守保密规范。保密义务不因..."), add a proper subject/definition sentence as transition.

7. 赔偿上限未删

Rule says "赔偿上限能删就删". Watch for bilateral clauses with caps (e.g. "违约金额为合同总金额的20%") — if it limits what our client can claim, delete it.

8. File naming with pre-existing【修】prefix

If the original file already has 【修】prefix (e.g. from previous editor), the delivered should technically be 【修】【修】... per strict rules. Record as known workflow defect.

Self-check before reporting "满意"

• Every WB INS/DEL reviewed against rules
• Full accepted text read for fluency (especially INS boundaries)
• rFonts cleaned (no hAnsi/cs/hint extras)
• Sub-numbering顺延 complete (not just chapter headings)
• Footer "法律顾问修订版" present in tracked change format
• No duplicate semantic content
• Heading style/format matches originals