Normalize shared reporting guidance to enforce h3+ headings and progressive disclosure

[Copilot]

A workflow-style audit found broad non-compliance in report output instructions: many workflows still used #/## headings and inconsistent guidance for collapsible detail sections. This change standardizes the shared reporting contract so importing workflows inherit compliant structure and formatting.

• Shared reporting contract update

  • Updated .github/workflows/shared/reporting.md to use ###-level section headings (or lower) in report instructions.
  • Kept report structure explicit: overview → key metrics/issues → collapsible detail → next actions.
  • Added concrete long-section guidance for lists/tables (>5 items) using <details> with bold summary text.

• Frontmatter correctness

  • Fixed frontmatter/content boundary in shared/reporting.md so the document remains valid and compiles cleanly.

• Compiled workflow sync

  • Regenerated affected .lock.yml files for workflows importing shared reporting guidance to keep compiled artifacts aligned with source instructions.

### Report structure guidelines

- Use `###` (or lower) headers only.
- For long lists/tables (>5 items), use:
  <details>
  <summary><b>View Details</b></summary>

  - item 1
  - item 2

  </details>

• Fixes [workflow-style] Normalize report formatting for non-compliant workflows #47079

[github-actions]

🤖 PR Triage

Field	Value
Category	formatting
Risk	medium
Score	33 / 100
Action	batch_review
Batch	pr-batch:workflow-formatting

Score breakdown: Impact 15 · Urgency 8 · Quality 10

Draft PR normalizing report formatting (h3+ headings) across 40+ workflow lock files + shared/reporting.md. Medium risk due to volume of lock file changes. No CI data. Batch with workflow changes (see #47107).

Generated by 🔧 PR Triage Agent · sonnet46 43.3 AIC · ⌖ 5.33 AIC · ⊞ 5.6K · ◷