[workflow-style] Normalize report formatting for non-compliant workflows #43389

Overview

Automated style normalization scan on 2026-07-04 identified 37 non-compliant reporting workflows out of 89 reviewed.

Non-compliant workflows are missing one or more of:

• h3+ header guidance — instructions must enforce ### or lower (never # or ##)
• Progressive disclosure — <details>/<summary> blocks for long content
• Report structure guidance — explicit output format instructions

Reference compliant examples: .github/workflows/daily-repo-chronicle.md, .github/workflows/audit-workflows.md

Non-Compliant Workflows

Required Changes

For each workflow above, add or update the Output Format section with:

1. h3+ headers — instruct the workflow to use ### or lower, never # or ##:

   Use ### (or lower) headers only.

2. Progressive disclosure — instruct the workflow to wrap long lists in <details>:

   Wrap long lists or details in <details><summary><b>View Details</b></summary>...</details>.

3. Report structure — add an explicit output format block:

   Structure reports as: overview → key metrics/issues → collapsible detail → next actions.

Example: Before / After

Before (missing all three):

## Output

List all findings here.

After (compliant):

### Output Format

Use `###` (or lower) headers only.

Structure reports as: overview → key metrics → collapsible detail → next actions.

Wrap long content with `<details><summary><b>View Details</b></summary>...</details>`.

Compliance Summary

References: §28707129682

network:
  allowed:
    - defaults
    - "awmgmcpg"

Generated by 🔧 Workflow Normalizer · 24.8 AIC · ⌖ 6.99 AIC · ⊞ 5.6K · ◷

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