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

[github-actions]

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

File	Issues
.github/workflows/agentic-token-audit.md	no report structure guidance
.github/workflows/agentic-token-trend-audit.md	no report structure guidance
.github/workflows/blog-auditor.md	no <details> progressive disclosure
.github/workflows/commit-changes-analyzer.md	no <details> progressive disclosure
.github/workflows/daily-ambient-context-optimizer.md	no report structure guidance
.github/workflows/daily-astrostylelite-markdown-spellcheck.md	no <details> progressive disclosure
.github/workflows/daily-caveman-optimizer.md	no <details> progressive disclosure, no report structure guidance
.github/workflows/daily-choice-test.md	no <details> progressive disclosure, no report structure guidance
.github/workflows/daily-community-attribution.md	no report structure guidance
.github/workflows/daily-compiler-threat-spec-optimizer.md	no <details> progressive disclosure
.github/workflows/daily-doc-healer.md	no report structure guidance
.github/workflows/daily-doc-updater.md	no report structure guidance
.github/workflows/daily-experiment-report.md	no report structure guidance
.github/workflows/daily-function-namer.md	no report structure guidance
.github/workflows/daily-geo-optimizer.md	no report structure guidance
.github/workflows/daily-hippo-learn.md	no report structure guidance
.github/workflows/daily-malicious-code-scan.md	no <details> progressive disclosure
.github/workflows/daily-model-inventory.md	no report structure guidance
.github/workflows/daily-multi-device-docs-tester.md	no report structure guidance
.github/workflows/daily-rendering-scripts-verifier.md	no report structure guidance
.github/workflows/daily-safe-output-integrator.md	no report structure guidance
.github/workflows/daily-safeoutputs-git-simulator.md	no report structure guidance
.github/workflows/daily-security-observability.md	no report structure guidance
.github/workflows/daily-semgrep-scan.md	no h3+ header guidance, no <details> progressive disclosure
.github/workflows/daily-skill-optimizer.md	no report structure guidance
.github/workflows/daily-syntax-error-quality.md	no report structure guidance
.github/workflows/daily-team-evolution-insights.md	no report structure guidance
.github/workflows/daily-workflow-updater.md	no report structure guidance
.github/workflows/daily-yamllint-fixer.md	no <details> progressive disclosure, no report structure guidance
.github/workflows/example-workflow-analyzer.md	no h3+ header guidance, no <details> progressive disclosure, no report structure guidance
.github/workflows/org-health-report.md	no report structure guidance
.github/workflows/pdf-summary.md	no report structure guidance
.github/workflows/ubuntu-image-analyzer.md	no <details> progressive disclosure, no report structure guidance
.github/workflows/video-analyzer.md	no <details> progressive disclosure
.github/workflows/weekly-blog-post-writer.md	no <details> progressive disclosure, no report structure guidance
.github/workflows/weekly-editors-health-check.md	no report structure guidance
.github/workflows/weekly-safe-outputs-spec-review.md	no report structure guidance

---

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

Category	Count
Total reviewed	89
✅ Compliant	52
⚠️ Non-compliant	37
Missing <details>	13
Missing report structure	30

Next Steps

• Update each non-compliant workflow file with the required Output Format section
• Re-run the style normalizer after updates to verify compliance
• Consider adding a linter check to make agent-report-progress to enforce style guidelines on new workflows

References: §28707129682

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 · 24.8 AIC · ⌖ 6.99 AIC · ⊞ 5.6K · ◷

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

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 1.75 AIC · ⌖ 6.25 AIC · ⊞ 7.3K · ◷