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

[github-actions]

Overview

Daily style review of agentic workflow prompts found 45 reporting workflows (of 146 scanned, excluding smoke-* test workflows) that don't follow the project's markdown formatting guidelines for generated reports: proper header hierarchy starting at ### (h3) or lower, and progressive disclosure via <details>/<summary> for long content.

Workflows reviewed: 146 (reporting-capable, non-smoke) · Non-compliant: 45

Non-Compliant Workflows

View all 45 non-compliant workflow files

File	Issue
.github/workflows/cloclo.md	No <details>, headers start at ##
.github/workflows/copilot-centralization-drilldown.md	No <details> usage
.github/workflows/copilot-centralization-optimizer.md	No <details> usage
.github/workflows/copilot-opt.md	Headers start at ##, no progressive disclosure
.github/workflows/craft.md	No <details> usage
.github/workflows/daily-arxiv-researcher.md	No progressive disclosure mention
.github/workflows/daily-pr-review-cursor.md	Headers use ##, no <details>
.github/workflows/daily-regression-audit-kiro.md	Headers use ##, no <details>
.github/workflows/daily-schema-audit-cursor.md	Headers use ##, no <details>
.github/workflows/daily-spec-coverage-kiro.md	Headers use ##, no <details>
.github/workflows/deepsec-security-scan.md	No <details> usage
.github/workflows/dependabot-burner.md	No <details> usage
.github/workflows/dependabot-go-checker.md	No <details> usage
.github/workflows/dev.md	No <details> usage
.github/workflows/duplicate-code-detector.md	Headers use ##, no <details>
.github/workflows/eslint-monster.md	No <details> usage
.github/workflows/eslint-refiner.md	No <details> usage
.github/workflows/example-failure-category-filter.md	No <details> usage
.github/workflows/go-pattern-detector.md	No <details> usage
.github/workflows/gpclean.md	No <details> usage
.github/workflows/issue-arborist.md	No progressive disclosure mention
.github/workflows/lint-monster.md	No <details> usage
.github/workflows/lockfile-stats.md	No <details> usage
.github/workflows/necromancer.md	No <details> usage
.github/workflows/poem-bot.md	No <details> usage
.github/workflows/portfolio-analyst.md	No progressive disclosure mention
.github/workflows/python-data-charts.md	No <details> usage
.github/workflows/refactoring-cadence.md	No <details> usage
.github/workflows/refiner.md	No <details> usage
.github/workflows/repo-tree-map.md	No <details> usage
.github/workflows/research.md	No <details> usage
.github/workflows/ruflo-backed-task.md	No <details> usage
.github/workflows/security-compliance.md	No progressive disclosure mention
.github/workflows/sergo.md	No <details> usage
.github/workflows/sighthound-security-scan.md	No <details> usage
.github/workflows/squad-game-planner.md	No <details> usage
.github/workflows/squad-plan.md	No <details> usage
.github/workflows/stale-repo-identifier.md	Headers use ##, no <details>
.github/workflows/sub-issue-closer.md	Headers use ### in body steps but no <details> for report output
.github/workflows/technical-doc-writer.md	No <details> usage
.github/workflows/uk-ai-operational-resilience.md	No <details> usage
.github/workflows/unbloat-docs.md	No <details> usage
.github/workflows/visual-regression-checker.md	No <details> usage
.github/workflows/workflow-health-manager.md	No progressive disclosure mention
.github/workflows/workflow-skill-extractor.md	No <details> usage

Required Changes

For each file above, add explicit reporting guidance to the prompt instructions:

1. Header hierarchy: Ensure any generated report content uses ### (h3) or lower — never #/## — to preserve document structure when embedded in issues/discussions/comments.
2. Progressive disclosure: Wrap long lists, detailed findings, logs, or tables in <details><summary><b>Label</b></summary> ... </details> blocks so summaries stay scannable.
3. Clear report structure: Follow the overview → key metrics → collapsible detail → next actions pattern, consistent with well-formed workflows in this repo.

Example: Progressive Disclosure Pattern

### Analysis Summary

**Items reviewed**: 42 · **Issues found**: 5

<details>
<summary><b>View detailed findings</b></summary>

1. **item-1**: description of issue
2. **item-2**: description of issue

</details>

### Next Steps

- [ ] Review findings
- [ ] Address high-priority items

Reference Good Examples

• .github/workflows/daily-repo-chronicle.md
• .github/workflows/audit-workflows.md

These follow h3+ header hierarchy, use <details> for progressive disclosure, and structure reports per the Style Guidelines (trust through clarity, user-focused, consistent experience).

Next Steps

• Review this consolidated list
• Update each identified workflow's prompt with header/<details>/report-structure guidance
• Recompile affected workflows (gh aw compile / make recompile)
• Monitor next daily normalization run for improved compliance

Note: /tmp/gh-aw/logs-cache/ (expected pre-cached 24h workflow-run data) was not present in this run's environment, so compliance analysis covers all reporting-capable workflow prompt files in .github/workflows/ (excluding smoke-* test workflows) rather than being scoped strictly to runs from the last 24 hours.

Generated by 🔧 Workflow Normalizer · auto · 37.1 AIC · ⌖ 2.69 AIC · ⊞ 10.5K · ◷

• expires on Aug 9, 2026, 5:05 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I have 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 · gpt54 · 1.58 AIC · ⌖ 4.95 AIC · ⊞ 8.4K · ◷