From ec928212949273f9ae643836caaf2fbc1ebb1d11 Mon Sep 17 00:00:00 2001
From: William Thorsen <william@thorsen.dev>
Date: Thu, 14 May 2026 04:53:10 -0700
Subject: [PATCH] agents|fix: Remove `<pre>` from update-jira-ticket allowlist

Removes `<pre>` from the elements permitted in `update_jira_issue` HTML payloads. Eliminates a class of opaque `INVALID_INPUT` failures that occurred when multi-line `<pre><code>` blocks contained quoted strings or apostrophes.

Multi-line code samples are now rendered as multiple `<p><code>` paragraphs or a single `<p>` with `<br>` separators and inline `<code>`. Single-line code continues to use inline `<code>` inside `<p>` or `<li>` as before.
---
 .../agents/content/skills/update-jira-ticket/SKILL.md  | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/packages/agents/content/skills/update-jira-ticket/SKILL.md b/packages/agents/content/skills/update-jira-ticket/SKILL.md
index c389daa0..ad10f501 100644
--- a/packages/agents/content/skills/update-jira-ticket/SKILL.md
+++ b/packages/agents/content/skills/update-jira-ticket/SKILL.md
@@ -20,7 +20,7 @@ Use whenever calling `update_jira_issue` (or `create_jira_issue`) with `descript
 
 Exhaustive list. Nothing else.
 
-`h1`, `h2`, `h3`, `h4`, `h5`, `h6`, `p`, `ul`, `ol`, `li`, `strong`, `em`, `code`, `pre`, `a`, `blockquote`, `hr`, `br`, `table`, `thead`, `tbody`, `tr`, `th`, `td`
+`h1`, `h2`, `h3`, `h4`, `h5`, `h6`, `p`, `ul`, `ol`, `li`, `strong`, `em`, `code`, `a`, `blockquote`, `hr`, `br`, `table`, `thead`, `tbody`, `tr`, `th`, `td`
 
 **Always strip `<ac:*>` and `<ri:*>` constructs unconditionally.** These are Confluence storage-format extensions: `<ac:*>` for Confluence elements like task lists and structured macros (e.g., `<ac:task-list>`, `<ac:structured-macro>`); `<ri:*>` for resource identifiers (e.g., `<ri:user>`, `<ri:page>`, `<ri:attachment>`). They have no Jira analogue, and including them produces `INVALID_INPUT`. If you have been working with Confluence content in the same session, audit the payload before sending.
 
@@ -54,6 +54,14 @@ The rule is symmetric — flipping the nesting order is not a workaround.
 <code>isDevMode</code> parameter
 ```
 
+### Multi-line code samples
+
+Do not wrap multi-line content in `<pre><code>`. The `<pre>` element is omitted from the allowlist entirely — multi-line `<pre><code>` blocks combining embedded newlines with quoted strings or apostrophes have been observed to trigger `INVALID_INPUT`.
+
+**Why:** ADF's `codeBlock` node accepts plain text, but the converter mishandles the combination of newlines and quote characters inside the `pre` block. Inline `<code>` in `<p>` survives the same characters, so the `<pre>` wrapper is the differentiator.
+
+**Workaround:** Render multi-line code as either multiple `<p><code>...</code></p>` paragraphs (one per logical line) or a single `<p>` with `<br>` separators between lines and inline `<code>` wrapping the code on each line. Single-line code is unchanged — continue to use inline `<code>` inside `<p>` or `<li>` as usual.
+
 ## Character handling
 
 Use **literal Unicode** in HTML. Do not use named HTML entities outside the three universally-safe ones.