Overview

A daily audit identified 75 of 87 reporting workflows that use #/## headers in their output instructions, violating the project style guideline requiring ### (h3) or lower. Several also lack <details> progressive disclosure patterns.

Why This Matters

Consistent formatting ensures:

• Proper document hierarchy when reports appear in issues/discussions
• Readable, scannable output with collapsible detail sections
• A predictable user experience across all workflow-generated reports

Style Guidelines to Apply

1. Headers: Use ### or lower — never # or ## in generated reports
2. Progressive Disclosure: Wrap long lists in <details><summary><b>Title</b></summary>...</details>
3. Report Structure: overview → key metrics → collapsible detail → next actions

Quick Fix Example

Before:

## Summary
Total: 42

## Details
- item1
- item2
- ...(long list)

After:

### Summary
Total: 42

<details>
<summary><b>View Details</b></summary>

- item1
- item2

</details>

Non-Compliant Workflows (75)

Required Changes per Workflow

For each file above:

1. Replace # Heading → ### Heading and ## Heading → ### Heading in report output instructions
2. Wrap lists/tables with >5 items in <details><summary><b>Title</b></summary>...</details>
3. Ensure structure follows: overview → key metrics → collapsible detail → next actions

Next Steps

• Prioritize high-frequency daily-* workflows
• Update header levels in output instructions
• Add <details> blocks for long content
• Re-run audit after updates to verify compliance

References: §29832904405

network:
  allowed:
    - defaults
    - "awmgmcpg"

Generated by 🔧 Workflow Normalizer · sonnet46 28.8 AIC · ⌖ 6.14 AIC · ⊞ 5.7K · ◷

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