v0.6.2

Patch release: insertion placement now follows authoring intent (ADR-0025).

Fixes

• append continues the section's text. It used to insert at the raw span end — after the blank lines separating the section from the next heading, gluing the new text to that heading (lead\n\nmore\n## B). It now backs up over the trailing whitespace-only lines to sit directly after the last non-blank line, leaving the separator in place (lead\nmore\n\n## B). A span ending at EOF keeps the literal end (matching append_notes); no separator is ever added or removed.
• insert_before/insert_after keep blank-line seams. Inserted sibling blocks were glued to both neighbours; they now get the same both-seams blank-line rule move already applied (only ever adds, never removes), via one shared implementation.

Notes

• Spans, content_hash, overlap footprints, and the wire schema are unchanged — only insertion offsets and seam padding moved. Byte-level output changes for callers that pinned the old placement.
• The edit_sections description now spells out placement, including the scope:"section" trap: plain text appended at a subtree's end structurally joins the last subsection — use scope:"body" for the section's own prose.