Normalize report formatting guidelines across 5 reporting workflows

.github/workflows/daily-otel-instrumentation-advisor.md

@@ -251,6 +251,10 @@ If you found a Sentry issue related to this problem, include the issue URL.>
 *Generated by the [Daily OTel Instrumentation Advisor](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) workflow*
 ```
 
+## Report Formatting Guidelines
+
+Use h3 (`###`) or lower for all headers in your report. Never use h1 (`#`) or h2 (`##`) — these are reserved for the issue title. Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to improve readability.
+
 ## Output Requirements
 
 You **MUST** call exactly one of these safe-output tools before finishing:

.github/workflows/daily-safe-outputs-conformance.md

@@ -121,7 +121,7 @@ Example: `SEC-001: Agent job in workflow X has write permissions`
 - **Handlers**: [List handler files if applicable]
 
 <details>
-<summary>🔍 Current vs Expected Behavior</summary>
+<summary><b>🔍 Current vs Expected Behavior</b></summary>
 
 ### Current Behavior
 
@@ -180,7 +180,7 @@ If multiple similar issues are found (e.g., 3 handlers missing the same validati
 
 ## Phase 4: Summary Report
 
-- **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.
+- **Report Formatting**: Use h3 (`###`) or lower for all headers in your report. Never use h1 (`#`) or h2 (`##`) — these are reserved for the issue title. Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to improve readability.
 
 After processing all issues, provide a summary in the workflow output:
 

.github/workflows/daily-secrets-analysis.md

@@ -292,7 +292,7 @@ For detailed information about secret usage patterns, see:
 
 ## Notes
 
-- **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.
+- **Report Formatting**: Use h3 (`###`) or lower for all headers in your report. Never use h1 (`#`) or h2 (`##`) — these are reserved for the issue title. Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to improve readability.
 - Focus on **trends and changes** rather than static inventory
 - Highlight **security concerns** prominently
 - Keep the report **concise but comprehensive**

.github/workflows/daily-skill-optimizer.md

@@ -179,4 +179,40 @@ The separate `skill_optimizer` job already ran `fastxyz/skill-optimizer` and pac
   - Expected impact for each improvement
 - Keep recommendations specific to this repository and immediately actionable.
 
+## Issue Format Guidelines
+
+Use h3 (`###`) or lower for all headers in your report. Never use h1 (`#`) or h2 (`##`) — these are reserved for the issue title.
+
+Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to improve readability. Example:
+
+```markdown
+<details>
+<summary><b>Full Analysis Details</b></summary>
+
+[Long detailed content here...]
+
+</details>
+```
+
+Structure the issue body as follows:
+
+```markdown
+### Summary
+- Run mode: dry-run / benchmark
+- Status: ✅/⚠️/❌
+
+### Key Findings
+[Always visible — the 3 improvements with expected impact]
+
+<details>
+<summary><b>Evidence from Artifact</b></summary>
+
+[Concrete references to artifact files and log excerpts]
+
+</details>
+
+### Recommendations
+[Numbered list of 3 actionable improvements]
+```
+
 Do not call `noop` for this workflow; always create exactly one issue with exactly 3 improvements.

.github/workflows/spec-librarian.md

@@ -267,7 +267,7 @@ The following packages have no README.md:
 The following specifications are outdated:
 
 <details>
-<summary>View stale specifications (N packages)</summary>
+<summary><b>View stale specifications (N packages)</b></summary>
 
 #### `parser` — Stale by 42 days
 
@@ -284,7 +284,7 @@ The following specifications are outdated:
 ### 🔄 Cross-Package Inconsistencies
 
 <details>
-<summary>View inconsistencies (N issues)</summary>
+<summary><b>View inconsistencies (N issues)</b></summary>
 
 #### Terminology Conflict
 
@@ -328,7 +328,7 @@ The following specifications are outdated:
 1. **Be thorough**: Check ALL packages, not just a sample
 2. **Be precise**: Reference exact file paths, function names, and dates
 3. **Be actionable**: Every finding should have a clear recommendation
-4. **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.
+4. **Report Formatting**: Use h3 (`###`) or lower for all headers in your report. Never use h1 (`#`) or h2 (`##`) — these are reserved for the issue title. Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to improve readability.
 5. **Use progressive disclosure**: Wrap details in `<details>` tags
 6. **One issue per run**: The `max: 1` limit ensures no issue spam
 7. **Skip if open**: The `skip-if-match` rule prevents duplicate issues