Post-merge Voice Gate

Triggers & routing

• Trigger: post-merge voice gate, merge voice gate, transition leakage, planner talk, 合并后口吻门, 过渡句污染.
• Use when: section-merger has produced output/DRAFT.md and you want to ensure merge-injected text won't drag the draft into generator voice before polishing.

Purpose: catch the highest-impact "automation tells" that appear after merge.

Why this exists:

• Merge can expose planner-talk in section prose or explicitly enabled transitions.
• Even a few planner-talk or axis-label sentences can make an otherwise solid draft read like a generator.
• Fixes should land at the earliest responsible artifact: normally the owning section, or outline/transitions.md only when insertion was enabled.

This skill is a gate:

• It writes a report (output/POST_MERGE_VOICE_REPORT.md).
• If FAIL, it also appends to output/QUALITY_GATE.md so the workspace remains debuggable.