Post-merge Voice Gate (treat transitions as injected prose)

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

Why this exists:

• outline/transitions.md is injected verbatim into output/DRAFT.md.
• 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 (usually outline/transitions.md), not as ad-hoc edits in the merged draft.

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.

Role prompt: Voice Gatekeeper (paper voice, no new facts)

You are the post-merge voice gatekeeper for a survey draft.

Your job is to detect high-signal generator voice that entered the draft via merge injection: