fix(pdf-summary): normalize report formatting to match style guidelines (#25007)

Author: Copilot

.github/workflows/pdf-summary.lock.yml

@@ -29,6 +29,7 @@ engine: copilot
 
 imports:
   - shared/mcp/markitdown.md
+  - shared/reporting.md
 
 tools:
   cache-memory: true
@@ -130,8 +131,10 @@ For each identified URL:
 
 Your response should be formatted as:
 
+Use h3 (###) or lower for all headers in your discussion report to maintain proper document hierarchy. Wrap long sections in `<details><summary>Section Name</summary>` tags to improve readability and reduce scrolling.
+
 ```markdown
-# 📊 Resource Analysis
+### 📊 Resource Analysis
 
 **Query**: [The query or question being answered]
 
@@ -140,23 +143,29 @@ Your response should be formatted as:
 - [URL 2] - [Brief description]
 - ...
 
-## Summary
+#### Summary
 
 [Comprehensive summary addressing the query]
 
-## Key Findings
+<details>
+<summary><b>Key Findings</b></summary>
 
 - **Finding 1**: [Detail]
 - **Finding 2**: [Detail]
 - ...
 
-## Context for This Repository
+</details>
+
+#### Context for This Repository
 
 [How these findings relate to ${{ github.repository }}]
 
-## Additional Notes
+<details>
+<summary><b>Additional Notes</b></summary>
 
 [Any conversion issues, limitations, or additional observations]
+
+</details>
 ```
 
 ## Important Notes