diff --git a/entry b/entry
index 9729904..80de177 100755
--- a/entry
+++ b/entry
@@ -147733,7 +147733,7 @@ An existing plan comment was found for this issue. Update that comment with the
 2. Delegate a subagent to analyze the diff and produce a structured summary. Include in its prompt:
    - the diff file path
    - PR metadata (title, file count, commit count, base/head branches)
-   - format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with before/after framing
+   - format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with plain-language \`##\` titles and before/after framing
    - instruct it to use the TOC to selectively read relevant diff sections, not the entire file
    - instruct it to return the full summary markdown via \`${ghPullfrogMcpName}/set_output\`
 3. After the subagent completes, call \`${ghPullfrogMcpName}/create_issue_comment\` with \`type: "Summary"\` and the summary body.
@@ -148657,7 +148657,7 @@ Do NOT overwrite a good comment with links/details with a generic message like "
 
 2. **ANALYZE** - Read the diff file. Use the TOC to selectively read relevant sections \u2014 do not read the entire file unless the PR is small.
 
-3. **SUMMARIZE** - Write a structured summary following the format from EVENT INSTRUCTIONS. If no format instructions are provided, produce a concise summary with a TL;DR, key changes list, and per-change sections with before/after framing.
+3. **SUMMARIZE** - Write a structured summary following the format from EVENT INSTRUCTIONS. If no format instructions are provided, produce a concise summary with a TL;DR, key changes list, and per-change sections with human-readable \`##\` titles and before/after framing.
 
 4. **POST** - Call ${ghPullfrogMcpName}/create_issue_comment with type: 'Summary' and the summary body.
 
diff --git a/mcp/selectMode.ts b/mcp/selectMode.ts
index 052dbd4..7c0eda2 100644
--- a/mcp/selectMode.ts
+++ b/mcp/selectMode.ts
@@ -193,7 +193,7 @@ An existing plan comment was found for this issue. Update that comment with the
 2. Delegate a subagent to analyze the diff and produce a structured summary. Include in its prompt:
    - the diff file path
    - PR metadata (title, file count, commit count, base/head branches)
-   - format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with before/after framing
+   - format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with plain-language \`##\` titles and before/after framing
    - instruct it to use the TOC to selectively read relevant diff sections, not the entire file
    - instruct it to return the full summary markdown via \`${ghPullfrogMcpName}/set_output\`
 3. After the subagent completes, call \`${ghPullfrogMcpName}/create_issue_comment\` with \`type: "Summary"\` and the summary body.
diff --git a/modes.ts b/modes.ts
index fcc2c34..4084190 100644
--- a/modes.ts
+++ b/modes.ts
@@ -322,7 +322,7 @@ Do NOT overwrite a good comment with links/details with a generic message like "
 
 2. **ANALYZE** - Read the diff file. Use the TOC to selectively read relevant sections — do not read the entire file unless the PR is small.
 
-3. **SUMMARIZE** - Write a structured summary following the format from EVENT INSTRUCTIONS. If no format instructions are provided, produce a concise summary with a TL;DR, key changes list, and per-change sections with before/after framing.
+3. **SUMMARIZE** - Write a structured summary following the format from EVENT INSTRUCTIONS. If no format instructions are provided, produce a concise summary with a TL;DR, key changes list, and per-change sections with human-readable \`##\` titles and before/after framing.
 
 4. **POST** - Call ${ghPullfrogMcpName}/create_issue_comment with type: 'Summary' and the summary body.