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

[github-actions]

Overview

Daily style normalization review identified 9 reporting workflows that do not explicitly instruct the agent to use ### (h3) or lower for all report headers. This is required because GitHub renders issue/discussion titles as h1, so agent-generated content must start at h3 to maintain proper document hierarchy.

Review period: Last 24 hours of workflow activity
Reviewed: 58 reporting workflows
Compliant: 49 ✅
Non-compliant: 9 ⚠️

---

Required Change (for each workflow below)

Add the following line to the output/report section of each workflow prompt:

Use `###` (h3) or lower for all headers in the report body. Never use `#` (h1) or `##` (h2) — these are reserved for the issue/discussion title rendered by GitHub.

If the workflow produces long lists, also add:

Wrap long sections (>5 items) in `<details><summary><b>Section Name</b></summary>` blocks.

Good reference examples: static-analysis-report.md, daily-repo-chronicle.md, audit-workflows.md

---

Non-Compliant Workflows

Workflow	Issue	File
daily-cli-performance	No h3 header mandate in report template	.github/workflows/daily-cli-performance.md
daily-community-attribution	No h3 header mandate in output section	.github/workflows/daily-community-attribution.md
daily-doc-healer	No h3 header mandate in report section	.github/workflows/daily-doc-healer.md
daily-geo-optimizer	Body template uses ## without h3 mandate	.github/workflows/daily-geo-optimizer.md
daily-multi-device-docs-tester	Issue body template missing h3 constraint	.github/workflows/daily-multi-device-docs-tester.md
daily-reliability-review	Progressive disclosure present but no explicit h3 mandate	.github/workflows/daily-reliability-review.md
daily-safeoutputs-git-simulator	Issue template missing h3 header guidance	.github/workflows/daily-safeoutputs-git-simulator.md
designer-drift-audit	Report output section missing h3 mandate	.github/workflows/designer-drift-audit.md
repo-audit-analyzer	Issue body template missing h3 constraint	.github/workflows/repo-audit-analyzer.md

Example: Before vs After

Before — no guidance given:

### Output
Create an issue with the following structure:
## Performance Summary
### Benchmarks
...

After — explicit h3 mandate:

### Output
Create an issue using `###` (h3) or lower for all headers. Never use `#` or `##` in the body.
Use `<details><summary><b>Section</b></summary>` to collapse sections longer than 5 items.

### Performance Summary
#### Benchmarks
...

Next Steps

• Update the 9 workflows above to include explicit h3 header mandate in their output/report sections
• For workflows generating long lists, also add <details> wrapping guidance
• Monitor next run to confirm compliance

References:

• §29334865423 — workflow run that generated this report

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 · 26.4 AIC · ⌖ 7.04 AIC · ⊞ 5.5K · ◷

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