[suite] [improvement] compose ticket bodies without a line limit and with light structure #78

open-ticket composes a ticket body as plain prose, and the agent writing it hard-wraps every line at the width it uses for Markdown files on disk. GitHub renders a single newline inside a paragraph as a line break, so the filed issue comes out as a ragged column of short lines that stops well short of the page width — #69 is the current example. Nothing in the skill asks for that wrapping, and the result is a ticket harder to read than the prose it was composed from.

The wanted outcome is a body the tracker renders the way it was written. The skill should say that a ticket body carries no line-length limit — a paragraph is one line, and a newline appears only where a break is meant. Alongside that, it should suggest that light structure and Markdown emphasis are welcome where they genuinely help a reader — a short list where the prose is already enumerating, emphasis on the one phrase carrying the point — while being explicit that this is a suggestion and not a target. A body dense with formatting is worse than the wall of prose it replaced, and the restraint the skill already demands of the content applies to its shape too.

One constraint already holds: open-thread quotes the body verbatim into the seed's ticket section, so whatever shape is chosen also has to read well quote-prefixed in a file on disk.