[WIP] Normalize 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

A review of 92 reporting/analysis workflows identified 65 non-compliant workflows that need formatting improvements to align with the project's markdown style guidelines.

Review Date: 2026-07-22
Workflows Reviewed: 92
Compliant: 11
Non-Compliant: 65

---

Required Changes

All non-compliant workflows need one or more of the following fixes:

1. Header levels: Replace # and ## headers in output instructions with ### or lower.
2. Progressive disclosure: Add <details><summary><b>...</b></summary> wrapping for long lists/tables.
3. Report structure guidance: Include explicit output structure: overview → metrics → collapsible detail → next actions.

Example: Progressive Disclosure Pattern

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

| File | Status | Notes |
|------|--------|-------|
| ... | ... | ... |

</details>

Reference good example: .github/workflows/daily-repo-chronicle.md, .github/workflows/audit-workflows.md

---

65 Non-Compliant Workflows — Full List

Workflow File	Issues
agentic-token-audit.md	uses h1/h2 headers, no report structure guidance
agentic-token-trend-audit.md	uses h1/h2 headers
api-consumption-report.md	uses h1/h2 headers
artifacts-summary.md	uses h1/h2 headers
audit-workflows.md	uses h1/h2 headers
blog-auditor.md	uses h1/h2 headers
copilot-agent-analysis.md	uses h1/h2 headers, no report structure guidance
copilot-pr-merged-report.md	uses h1/h2 headers, no report structure guidance
copilot-pr-nlp-analysis.md	uses h1/h2 headers, no report structure guidance
copilot-pr-prompt-analysis.md	uses h1/h2 headers
daily-agentrx-trace-optimizer.md	uses h1/h2 headers
daily-ambient-context-optimizer.md	uses h1/h2 headers, no report structure guidance
daily-architecture-diagram.md	uses h1/h2 headers
daily-aw-cross-repo-compile-check.md	uses h1/h2 headers, no report structure guidance
daily-awf-spec-compiler-surfacing.md	uses h1/h2 headers, no report structure guidance
daily-cache-strategy-analyzer.md	uses h1/h2 headers, no report structure guidance
daily-cli-performance.md	uses h1/h2 headers, no report structure guidance
daily-cli-tools-tester.md	uses h1/h2 headers
daily-code-metrics.md	uses h1/h2 headers
daily-community-attribution.md	uses h1/h2 headers
daily-compiler-quality.md	uses h1/h2 headers
daily-doc-healer.md	uses h1/h2 headers
daily-evals-report.md	uses h1/h2 headers, no report structure guidance
daily-experiment-report.md	uses h1/h2 headers
daily-file-diet.md	uses h1/h2 headers
daily-firewall-report.md	uses h1/h2 headers
daily-formal-spec-verifier.md	uses h1/h2 headers, no report structure guidance
daily-function-namer.md	uses h1/h2 headers
daily-geo-optimizer.md	uses h1/h2 headers
daily-hippo-learn.md	uses h1/h2 headers
daily-issues-report.md	uses h1/h2 headers
daily-mcp-concurrency-analysis.md	uses h1/h2 headers, no report structure guidance
daily-model-inventory.md	uses h1/h2 headers
daily-model-resolution.md	uses h1/h2 headers
daily-multi-device-docs-tester.md	uses h1/h2 headers
daily-news.md	uses h1/h2 headers, no report structure guidance
daily-observability-report.md	uses h1/h2 headers
daily-performance-summary.md	uses h1/h2 headers
daily-regulatory.md	uses h1/h2 headers
daily-reliability-review.md	uses h1/h2 headers, no report structure guidance
daily-repo-chronicle.md	uses h1/h2 headers
daily-safe-output-optimizer.md	uses h1/h2 headers
daily-safe-outputs-conformance.md	uses h1/h2 headers
daily-safeoutputs-git-simulator.md	uses h1/h2 headers
daily-secrets-analysis.md	uses h1/h2 headers
daily-security-observability.md	uses h1/h2 headers
daily-security-red-team.md	uses h1/h2 headers
daily-sentrux-report.md	uses h1/h2 headers, no report structure guidance
daily-skill-optimizer.md	uses h1/h2 headers
daily-spdd-spec-planner.md	uses h1/h2 headers, no report structure guidance
daily-syntax-error-quality.md	uses h1/h2 headers
daily-team-evolution-insights.md	uses h1/h2 headers
daily-team-status.md	uses h1/h2 headers
daily-testify-uber-super-expert.md	uses h1/h2 headers, no report structure guidance
daily-token-consumption-report.md	uses h1/h2 headers, no report structure guidance
daily-vulnhunter-scan.md	uses h1/h2 headers, no <details>, no report structure guidance
designer-drift-audit.md	uses h1/h2 headers, no report structure guidance
github-mcp-structural-analysis.md	uses h1/h2 headers, no report structure guidance
github-mcp-tools-report.md	uses h1/h2 headers, no report structure guidance
org-health-report.md	uses h1/h2 headers
pdf-summary.md	uses h1/h2 headers
prompt-clustering-analysis.md	uses h1/h2 headers, no report structure guidance
repo-audit-analyzer.md	uses h1/h2 headers, no report structure guidance
static-analysis-report.md	uses h1/h2 headers, no report structure guidance
weekly-issue-summary.md	uses h1/h2 headers

---

Next Steps

• Update each workflow prompt to use ###/#### headers instead of #/##
• Add <details> wrappers around long lists/tables in report output templates
• Add explicit report structure guidance (overview → metrics → collapsible details → next actions)
• Re-run this normalizer workflow after updates 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 · sonnet46 25.5 AIC · ⌖ 6.86 AIC · ⊞ 5.8K · ◷

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

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

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

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