Normalize progressive-disclosure guidance across reporting workflows

.github/workflows/daily-code-metrics.md

@@ -202,13 +202,23 @@ For each metric: current value, 7-day % change, 30-day % change, trend indicator
 
 Use detailed template with embedded visualization charts:
 
+**Report Structure Guidelines**
+
+- Use `###` (or lower) headers only.
+- Keep summary and critical actions visible; move long detail into `<details>` blocks.
+- Structure reports as: overview → key metrics/issues → collapsible detail → next actions.
+
 ### Discussion Structure
 
 - **Title**: `Daily Code Metrics Report - YYYY-MM-DD`
 - **Body template**:
 
 ```markdown
 {{#if experiments.output_format == 'executive_summary' }}
+### Summary
+
+**X items found** — [brief description]
+
 **Key metrics today**: LOC: X,XXX | Quality score: XX/100 | Test ratio: X.XX | Active files (7d): XXX
 
 ### 📊 Key Visualizations
@@ -224,14 +234,18 @@ Use detailed template with embedded visualization charts:
 
 *For full metric tables, switch to `full_detail` variant.*
 {{else}}
+### Summary
+
+**X items found** — [brief description]
+
 Brief 2-3 paragraph executive summary highlighting key findings, quality score, notable trends, and any concerns requiring attention.
 
 ### 📊 Visualizations
 
 Embed all 6 charts (LOC by Language, Top Directories, Quality Score, Test Coverage, Code Churn, Historical Trends) with a brief analysis sentence each.
 
 <details>
-<summary>📈 Detailed Metrics</summary>
+<summary><b>View Full Details</b></summary>
 
 One compact table per category (Size, Quality, Tests, Churn-source, Churn-generated, Workflows/Docs). Follow with a Quality Score breakdown (Test Coverage 30%, Code Organization 25%, Documentation 20%, Churn Stability 15%, Comment Density 10%) and 3–5 actionable recommendations.
 

.github/workflows/daily-issues-report.md

@@ -273,17 +273,27 @@ Create a new discussion with the comprehensive report.
 
 **Formatting Guideline**: Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy. The discussion title serves as h1, so all content headers should start at h3.
 
+**Report Structure Guidelines**
+
+- Use `###` (or lower) headers only.
+- Keep summary and critical actions visible; move long detail into `<details>` blocks.
+- Structure reports as: overview → key metrics/issues → collapsible detail → next actions.
+
 ### Discussion Format
 
 **Title**: `[daily issues] Daily Issues Report - YYYY-MM-DD`
 
 **Body**:
 
 ```markdown
+### Summary
+
+**X items found** — [brief description]
+
 Brief 2-3 paragraph summary of key findings: total issues analyzed, main clusters identified, notable trends, and any concerns that need attention.
 
 {{#if experiments.output_format == 'collapsible'}}<details>
-<summary>📊 Full Report Details</summary>{{/if}}
+<summary><b>View Full Details</b></summary>{{/if}}
 
 ### 📈 Issue Activity Trends
 

.github/workflows/daily-malicious-code-scan.md

@@ -256,6 +256,12 @@ A successful malicious code scan:
 
 Your output MUST:
 
+**Report Structure Guidelines**
+
+- Use `###` (or lower) headers only.
+- Keep summary and critical actions visible; move long detail into `<details>` blocks.
+- Structure reports as: overview → key metrics/issues → collapsible detail → next actions.
+
 1. **If suspicious patterns are found**:
    - **CALL** the `create_code_scanning_alert` tool for each finding
    - Each alert must include: rule_id, message, severity, file_path, start_line, description
@@ -280,6 +286,21 @@ Your output MUST:
    - Types of patterns searched for
    - Confidence level of findings
 
+### Example Summary Format
+
+```markdown
+### Summary
+
+**X items found** — [brief description]
+
+<details>
+<summary><b>View Full Details</b></summary>
+
+... detailed content here ...
+
+</details>
+```
+
 ## Example Alert Output
 
 ```json

.github/workflows/daily-model-inventory.md

@@ -670,4 +670,21 @@ coverage is up to date.
 
 ### Output Format
 
-Structure reports as: overview → key metrics/issues → collapsible detail → next actions.
+**Report Structure Guidelines**
+
+- Use `###` (or lower) headers only.
+- Keep summary and critical actions visible; move long detail into `<details>` blocks.
+- Structure reports as: overview → key metrics/issues → collapsible detail → next actions.
+
+```markdown
+### Summary
+
+**X items found** — [brief description]
+
+<details>
+<summary><b>View Full Details</b></summary>
+
+... detailed content here ...
+
+</details>
+```