section-merger

name

section-merger

description

Deterministically merge the final fingerprinted section snapshot into `output/DRAFT.md`, preserving outline order and inserting transitions only when explicitly enabled. **Trigger**: merge sections, merge draft, combine section files, sections/ -> output/DRAFT.md, 合并小节, 拼接草稿. **Use when**: you have per-unit prose files under `sections/` and want a single `output/DRAFT.md` for polishing/review/LaTeX.

Section Merger

Goal: assemble a paper-like output/DRAFT.md from:

• sections/ (per-section/per-subsection prose)
• outline/transitions.md (optional hand-off suggestions; generated by transition-weaver)
• outline/tables_appendix.md (reader-facing Appendix tables; generated by appendix-table-writer)

Merge order is driven by outline/outline.yml. The draft title is derived from GOAL.md when present. When sections/sections_manifest.jsonl is supplied by the Pipeline contract, every merged section must match its recorded bytes and SHA-256 hash.

This skill is deterministic: it does not rewrite content or invent prose; it only merges already-generated artifacts.

Transitions (explicit opt-in)

• By default, generated transitions are not inserted.
• To insert H3 transitions, create outline/transitions.insert_h3.ok.
• To insert H2 transitions, create outline/transitions.insert_h2.ok.
• Format contract: H3 entries use - 3.1 -> 3.2: <text>.
• Compatibility: → is accepted, but -> is the preferred contract (avoids control-character encoding issues).
• Treat transitions as injected draft text: run post-merge-voice-gate after merging, and route fixes back to (do not patch the merged draft).