Add explicit h3 formatting enforcement to 3 non-compliant reporting workflows

.github/workflows/daily-reliability-review.md

@@ -107,6 +107,8 @@ Order findings by:
 
 ## Output
 
+**Report Formatting**: Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy. Wrap long sections in `<details><summary>Section Name</summary>` tags to improve readability and reduce scrolling.
+
 Create exactly one GitHub issue.
 
 Title:

.github/workflows/daily-team-evolution-insights.md

@@ -236,6 +236,8 @@ Always create a GitHub Discussion with your findings using this structure:
 
 ### Formatting Guidelines
 
+**Report Formatting**: Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy. Wrap long sections in `<details><summary>Section Name</summary>` tags to improve readability and reduce scrolling.
+
 **Progressive Disclosure**: For sections with extensive details, use expandable sections to keep the report scannable while maintaining completeness.
 
 **Syntax for expandable sections**:

.github/workflows/detection-analysis-report.md

@@ -125,6 +125,8 @@ If `/tmp/gh-aw/python/charts/detection_trend.png` was generated, upload it with
 
 ## Report Structure
 
+**Report Formatting**: Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy. Wrap long sections in `<details><summary>Section Name</summary>` tags to improve readability and reduce scrolling.
+
 Publish a discussion using the configured safe-output. Structure the body as:
 
 ### Summary