Normalize report body formatting rules across 11 reporting workflows

.github/workflows/copilot-agent-analysis.md

@@ -207,6 +207,10 @@ Create a **concise** discussion with your findings using the safe-outputs create
 
 **Discussion Title**: `Daily Copilot Agent Analysis - [DATE]`
 
+Use `###` or lower for all headers in your report. Never use `#` (h1) or `##` (h2) — these are reserved for the discussion title rendered by GitHub.
+
+Wrap long sections (>5 items, detailed lists, raw data) in `<details><summary><b>Section Name</b></summary>` blocks to keep the report scannable.
+
 **Shared Discussion Structure** (both variants):
 ```markdown
 ### 🤖 Copilot Agent PR Analysis - [DATE]

.github/workflows/copilot-pr-merged-report.md

@@ -150,6 +150,10 @@ For token usage information, we need to find the workflow run associated with th
 
 Create a concise report with the following structure:
 
+Use `###` or lower for all headers in your report. Never use `#` (h1) or `##` (h2) — these are reserved for the discussion title rendered by GitHub.
+
+Wrap long sections (>5 items, detailed lists, raw data) in `<details><summary><b>Section Name</b></summary>` blocks to keep the report scannable.
+
 ```markdown
 ### 🤖 Daily Copilot PR Merged Report - [DATE]
 
@@ -169,7 +173,7 @@ Create a concise report with the following structure:
 - Any PRs with exceptional metrics (very large, many test files, etc.)
 
 <details>
-<summary>Merged Pull Requests</summary>
+<summary><b>Merged Pull Requests</b></summary>
 
 | PR # | Title | Lines Added | Lines Deleted | Test Files | Merged At |
 |------|-------|-------------|---------------|------------|-----------|
@@ -178,7 +182,7 @@ Create a concise report with the following structure:
 </details>
 
 <details>
-<summary>Code Generation Metrics</summary>
+<summary><b>Code Generation Metrics</b></summary>
 
 - **Production Code**: [lines added - test lines added] lines
 - **Test Code**: [test lines added] lines

.github/workflows/copilot-pr-nlp-analysis.md

@@ -269,6 +269,8 @@ Post a comprehensive discussion with the following structure:
 
 Use h3 (`###`) or lower for all headers in the discussion body. Never use h1 (`#`) or h2 (`##`) — these are reserved for the GitHub Discussion title rendered by the platform.
 
+Wrap long sections (>5 items, detailed lists, raw data) in `<details><summary><b>Section Name</b></summary>` blocks to keep the report scannable.
+
 **Content Template** (substitute `[SENTIMENT_DIST_URL]`, `[SENTIMENT_TIME_URL]`, `[TOPIC_FREQ_URL]`, `[TOPICS_CLOUD_URL]`, and `[KEYWORD_TRENDS_URL]` with the literal URL strings read by Python from the files above):
 ````markdown
 ### 🤖 Copilot PR Conversation NLP Analysis - [DATE]

.github/workflows/daily-agentrx-trace-optimizer.md

@@ -163,6 +163,10 @@ Create exactly one issue titled:
 
 `[agentrx-optimizer] Daily Workflow Optimization - YYYY-MM-DD`
 
+Use `###` or lower for all headers in your report. Never use `#` (h1) or `##` (h2) — these are reserved for the issue title rendered by GitHub.
+
+Wrap long sections (>5 items, detailed lists, raw data) in `<details><summary><b>Section Name</b></summary>` blocks to keep the report scannable.
+
 Body structure:
 
 ### Executive Summary
@@ -175,7 +179,7 @@ Body structure:
 - Representative run IDs
 
 <details>
-<summary>AgentRx Artifacts</summary>
+<summary><b>AgentRx Artifacts</b></summary>
 
 {{#if experiments.sub_agent_strategy == 'sub_agents'}}
 Invoke `artifacts-summarizer` by passing this exact input block: