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

[github-actions]

Overview

This issue tracks 9 reporting workflows that need markdown style updates to follow the project's formatting guidelines. The changes are small but impactful — they help readers consume reports faster and reduce scrolling.

Reviewed: 28 reporting workflows
Non-compliant: 9 workflows
Issues: Missing h3 header guidance and/or <details> progressive disclosure instructions

---

Non-Compliant Workflows

Workflow	Issue
daily-issues-report	Missing progressive disclosure (<details>) guidance
daily-code-metrics	Missing progressive disclosure guidance
daily-security-observability	Missing progressive disclosure guidance
daily-malicious-code-scan	Missing progressive disclosure guidance
org-health-report	Missing progressive disclosure guidance
daily-model-inventory	Missing progressive disclosure guidance
daily-team-evolution-insights	Missing h3 header level guidance
daily-community-attribution	Missing h3 header level guidance
daily-reliability-review	Missing h3 header level guidance

---

Required Changes

Each non-compliant workflow prompt needs a Report Formatting note in its output/report section. The minimal addition per workflow:

For missing progressive disclosure — add to the report quality or output section:

- **Report Formatting**: Use h3 (###) or lower for all headers. Wrap long sections in `<details><summary><b>Section Name</b></summary>` tags to reduce scrolling.

For missing h3 guidance — add to the output section:

- **Report Formatting**: Use h3 (###) or lower for all headers in your report. Wrap verbose details in `<details><summary><b>View Details</b></summary>` blocks so critical information stays visible.

---

Progressive Disclosure Example

Before / After

Before (forces scrolling, buries critical info):

## Summary
...

## All Items (50 entries)
- item 1
- item 2
... (long list)

## Recommendations
...

After (critical info visible, details collapsible):

### Summary
...

### Recommendations
...

<details>
<summary><b>All Items (50 entries)</b></summary>

- item 1
- item 2
... (long list)

</details>

---

Good Reference Examples

• .github/workflows/daily-observability-report.md — explicit h3 + <details> instructions
• .github/workflows/daily-token-consumption-report.md — progressive disclosure guidance
• .github/workflows/audit-workflows.md — well-structured report formatting

---

Checklist

• daily-issues-report — add progressive disclosure guidance
• daily-code-metrics — add progressive disclosure guidance
• daily-security-observability — add progressive disclosure guidance
• daily-malicious-code-scan — add progressive disclosure guidance
• org-health-report — add progressive disclosure guidance
• daily-model-inventory — add progressive disclosure guidance
• daily-team-evolution-insights — add h3 header guidance
• daily-community-attribution — add h3 header guidance
• daily-reliability-review — add h3 header guidance

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 · 32.6 AIC · ⌖ 5.98 AIC · ⊞ 5.5K · ◷

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