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

[Copilot]

pdf-summary.md used #/## headers in its response template and lacked progressive disclosure — diverging from the reporting conventions followed by other daily/weekly report workflows.

Changes

• Import shared/reporting.md — pulls in header-level and <details> guidelines automatically
• Downgrade headers — response template # → ###, ## → ####
• Progressive disclosure — wrap verbose sections ("Key Findings", "Additional Notes") in <details><summary>…</summary> blocks
• Explicit formatting instruction — added inline guidance before the template block so the agent knows to apply these rules at generation time
• Recompile — pdf-summary.lock.yml regenerated to reflect the updated markdown

Before / After (response template)

-# 📊 Resource Analysis
+### 📊 Resource Analysis
 
-## Key Findings
-- **Finding 1**: ...
+<details>
+<summary><b>Key Findings</b></summary>
+
+- **Finding 1**: ...
+
+</details>

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://github.com/api/graphql
  • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw (http block)
  • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw FASAOyC/MW4J11fm-1 (http block)
• https://github.com/api/repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b
  • Triggering command: /usr/bin/gh gh api /repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b --jq .object.sha (http block)
• https://github.com/api/repos/github/gh-aw
  • Triggering command: /usr/bin/gh gh api /repos/github/gh-aw --jq .visibility (http block)
• https://github.com/api/repos/githubnext/agentics/git/ref/tags/-
  • Triggering command: /usr/bin/gh gh api /repos/githubnext/agentics/git/ref/tags/- --jq .object.sha (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

Normalizes the pdf-summary workflow’s generated report formatting to match the repository’s reporting conventions (header hierarchy + progressive disclosure).

Changes:

• Imports shared/reporting.md into the pdf-summary prompt.
• Updates the response template to use ###/#### headers and wraps verbose sections in <details> blocks.
• Regenerates .github/workflows/pdf-summary.lock.yml to reflect the updated prompt content/imports.

Show a summary per file

File	Description
.github/workflows/pdf-summary.md	Adds shared/reporting.md import and adjusts the response template to use lower-level headers and <details> sections.
.github/workflows/pdf-summary.lock.yml	Regenerated lockfile to include the new import and updated prompt hash/embedded prompt content.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

The new formatting instruction says “Use h3 (###) or lower for all headers in your discussion report…”, but this workflow also posts the response as an issue/PR comment (and optionally creates a discussion). To avoid the agent treating the header rule as discussion-only, consider aligning wording with existing workflows that apply it to all report outputs (e.g., .github/workflows/cli-version-checker.md:181 uses “Use h3 (###) or lower for all headers.”).

Suggested change

	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.
	Use h3 (###) or lower for all headers to maintain proper document hierarchy. Wrap long sections in `<details><summary>Section Name</summary>` tags to improve readability and reduce scrolling.