[WIP] Fix normalization of report formatting for non-compliant workflows

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

---

This section details on the original issue you should resolve

<issue_title>[workflow-style] Normalize report formatting for non-compliant workflows</issue_title>
<issue_description>### Overview

Style review of 85 reporting workflows identified 13 non-compliant workflows whose output templates or structure use # (h1) or ## (h2) headers instead of ### (h3) or lower. This violates the Report Structure Guidelines that require all generated reports to start at h3 to maintain proper document hierarchy within GitHub issues and discussions.

Period: Last 24 hours (2026-07-20)
Workflows Reviewed: 85
Non-Compliant: 13
Reference (compliant example): .github/workflows/daily-repo-chronicle.md, .github/workflows/audit-workflows.md

---

Non-Compliant Workflows

Workflow	File	Issue
artifacts-summary	.github/workflows/artifacts-summary.md	Output template uses # Artifacts Usage Report and ## Insights & Recommendations
blog-auditor	.github/workflows/blog-auditor.md	Output template uses ## ✅ Agentic Workflows Blog Audit - PASSED (h2)
daily-architecture-diagram	.github/workflows/daily-architecture-diagram.md	Output template uses # Architecture Diagram and ## Overview
daily-community-attribution	.github/workflows/daily-community-attribution.md	Output template uses h1/h2 headers
daily-formal-spec-verifier	.github/workflows/daily-formal-spec-verifier.md	Output template uses h1/h2 headers
daily-geo-optimizer	.github/workflows/daily-geo-optimizer.md	Output template uses h1/h2 headers
daily-safeoutputs-git-simulator	.github/workflows/daily-safeoutputs-git-simulator.md	Output template uses h1/h2 headers
daily-security-observability	.github/workflows/daily-security-observability.md	Output template uses h1/h2 headers
daily-team-evolution-insights	.github/workflows/daily-team-evolution-insights.md	Output template uses h1/h2 headers
daily-vulnhunter-scan	.github/workflows/daily-vulnhunter-scan.md	Workflow structure uses h1/h2 throughout, no h3+ guidance
daily-yamllint-fixer	.github/workflows/daily-yamllint-fixer.md	Output template uses h1/h2 headers
repo-audit-analyzer	.github/workflows/repo-audit-analyzer.md	Output template uses h1/h2 headers
weekly-blog-post-writer	.github/workflows/weekly-blog-post-writer.md	Output template uses h1/h2 headers

---

Required Changes

For each workflow above, apply these fixes:

1. Downgrade output template headers

❌ Before:

# Report Title
## Section Heading

✅ After:

### Report Title
#### Section Heading

2. Add progressive disclosure for long content

Where output templates contain long lists or tables, wrap with <details>:

<details>
<summary><b>View Detailed Findings</b></summary>

| Column | Value |
|--------|-------|
| ...    | ...   |

</details>

3. Add explicit output format guidance (where missing)

Add to the workflow prompt:

Use `###` or lower headings in all generated output.
Wrap long sections in `<details><summary><b>Title</b></summary>...</details>`.

---

Compliant Reference Examples

daily-repo-chronicle.md — uses ### headers throughout, wraps details in <details> blocks.

audit-workflows.md — clear ### Output Format section with h3+ only, progressive disclosure guidance.

daily-elixir-credo-snippet-audit.md (recently fixed) — explicit instruction:

Use ### or lower headings. Wrap long details in <details><summary><b>View Details</b></summary>...</details>.

---

Next Steps

• Update each workflow listed above to downgrade h1/h2 to h3+
• Add <details> wrapping guidance where output sections are long
• Re-run workflow-style-normalizer after changes to verify compliance

[!WARNING]

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔧 Workflow Normalizer · 38.8 AIC · ⌖ 4.96 AIC · ⊞ 5.8K · ◷

• expires on Jul 21, 2026, 5:26 AM UTC-08:00

• Closes [workflow-style] Normalize report formatting for non-compliant workflows #46838

Comments on the Issue (you are @copilot in this section)

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

[github-actions]

Thanks for working on this! 🔧

This PR is a work-in-progress that details the plan to normalize report formatting across 13 non-compliant workflows. Great job documenting the scope with a clear table of affected workflows and before/after examples.

A few notes as work progresses:

• No code changes yet — The PR currently has 0 additions/deletions. Once fixes are ready, commit them to this branch and the diff will populate.
• Tests missing — When you add the header and <details> normalization changes, include unit or integration tests that verify the updated workflows generate compliant output.
• Process check ✅ — Since this PR is opened by the core team agent (copilot-swe-agent), it follows the project's contribution model (core team agents handle PRs; community contributes via detailed issue plans).

Once code lands, feel free to mark the WIP status as complete!

Generated by ✅ Contribution Check · 50.7 AIC · ⌖ 11.5 AIC · ⊞ 6.2K · ◷