idd-issue --from-discussion quotes third-party text by a prose rule only — one unquoted line can hide a real blocker from the gate #372

Problem

idd-issue --from-discussion copies a GitHub Discussion's opening post — written by any account — into the new issue's body, above the ## Current Status block. The only thing that keeps that third-party text from acting as issue structure is a prose rule in the skill: prefix every copied line with >. The model applies it line by line; nothing mechanical does.

The round-6 verify of PR #318 measured what a single unquoted line does. A lazy-continuation line inside the quote, `````x``` is how I wrote it``, is one of the actionability reader's documented fence divergences (an opener whose info string contains a backtick). The reader opens a fence that never closes and returns no ### Blocking — while GitHub, through markdown-it, still renders the real `### Blocking` section with its blocker. A third-party post can therefore hide a real blocker from the gate. When every line carries `>`, the reader reads the blocker correctly.

Expected

• The seed text is quoted mechanically, e.g. sed 's/^/> /' (or an equivalent that also handles blank lines), not by a per-line prose instruction.
• A test feeds an opening post containing the shape above and asserts the gate still reports the issue's own ### Blocking.

Source

• PR feat: actionability gate round 2 — prefix tier + deferral vocabulary, wired into all four consumers (#316) #318 round-6 verify, follow-up row 14 (security S3, Devil's Advocate DA-3(4)). Report: feat: actionability gate round 2 — prefix tier + deferral vocabulary, wired into all four consumers (#316) #318 (comment)

Complexity

Simple — one quoting step in idd-issue, one test.