Soft-wrapped paragraphs converted to hard `<p>` breaks on sync

Affected: Plane Cloud, official GitHub integration. See also: meta-issue on destructive overwrite (issue 01).

Symptom

Issue or comment bodies whose paragraphs are soft-wrapped at ~80 characters with literal newlines have those internal newlines turned into hard paragraph breaks after a sync round-trip.

Input: body wraps at ~80 characters with literal \n inside paragraphs (a common convention for human-written markdown).

Pushed back to GH markdown: internal newlines become hard <p> breaks, turning soft-wrapped prose into a sequence of single-line paragraphs that read very differently from the original.

Impact

Lower severity than the other patterns — the text content is preserved, just reformatted. But the reformatting is unwanted and visible to anyone using deliberate soft wrapping.

Ask

Treat single \n inside a paragraph as soft-wrap (or non-significant whitespace), matching GitHub-Flavoured Markdown's default rendering. Only treat blank lines (\n\n) as paragraph separators.

Reproduction

1. Connect a GitHub repo to a Plane workspace via the official GitHub integration. Set sync to bidirectional.
2. Create a GitHub issue whose body contains a single paragraph wrapped over multiple lines (no blank lines inside the paragraph). Apply the Plane label.
3. To exercise the destructive Plane→GH push, follow the trigger recipe in meta-issue 01.

Start with the official GitHub integration's bidirectional sync flow and reproduce the issue using a soft-wrapped paragraph with no blank lines. Trace how the body is pushed back to GitHub markdown; done means single newlines remain within a paragraph while blank lines still separate paragraphs.