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

[github-actions]

This issue consolidates markdown style violations found across daily/weekly reporting workflows during routine normalization review on 2026-06-10. All workflows below generate user-facing reports (issues, discussions, comments) but do not follow the project's Report Structure Guidelines.

Summary

Category	Count
Total reporting workflows reviewed	63
✅ Compliant	19
⚠️ Needs Improvement (1 gap)	30
❌ Non-Compliant (2+ gaps)	14

Required Style Standards

All report-generating workflows must guide the agent to:

1. Use ### (h3) or lower for all headers in generated reports — never # or ##
2. Use <details><summary>...</summary> tags to wrap verbose sections (logs, per-item breakdowns, raw data)
3. Follow the report structure pattern: Overview → Critical Info → <details> for verbose data → Recommendations

Non-Compliant Workflows

The following 14 workflows are missing two or more of the required style elements:

File	Missing h3 guidance	Missing <details>	Missing report structure
.github/workflows/daily-assign-issue-to-user.md	❌	❌	❌
.github/workflows/daily-byok-ollama-test.md	✅	❌	❌
.github/workflows/daily-choice-test.md	✅	❌	❌
.github/workflows/daily-compiler-threat-spec-optimizer.md	✅	❌	❌
.github/workflows/daily-credit-limit-test.md	❌	❌	❌
.github/workflows/daily-fact.md	❌	❌	✅
.github/workflows/daily-malicious-code-scan.md	✅	❌	❌
.github/workflows/daily-max-ai-credits-test.md	❌	❌	❌
.github/workflows/daily-rendering-scripts-verifier.md	✅	❌	❌
.github/workflows/daily-security-red-team.md	✅	❌	❌
.github/workflows/daily-semgrep-scan.md	❌	❌	✅
.github/workflows/daily-team-status.md	❌	❌	❌
.github/workflows/daily-windows-terminal-integration-builder.md	✅	❌	❌
.github/workflows/weekly-blog-post-writer.md	✅	❌	❌

Required Changes Per Workflow

Each non-compliant workflow needs an Output Format section added to its prompt. Use this template:

## Output Format

Create a report following these guidelines:
- Use `###` (h3) or lower for all headers — never `#` or `##`
- Wrap verbose details in `<details><summary><b>View Details</b></summary>` blocks
- Structure: **Overview** → **Key Findings** → `<details>` for full data → **Recommendations**

Example: Before vs After

Before (non-compliant prompt excerpt):

Create a daily report with sections for each finding. Include a full log of all items checked.

After (compliant prompt excerpt, modeled on daily-repo-chronicle.md):

## Output Format

Create a report following these guidelines:
- Use `###` (h3) or lower for all headers — never `#` or `##`
- Lead with a one-paragraph summary of key findings
- Wrap the full item list in `<details><summary><b>View All Items</b></summary>` 
- End with actionable **Recommendations** or **Next Steps**

Reference: Good Examples in This Repository

These workflows already follow the style guidelines and can serve as models:

• daily-repo-chronicle.md — uses ### headers, <details> for verbose logs, clear report structure
• audit-workflows.md — uses progressive disclosure and consistent section layout

View All 30 "Needs Improvement" Workflows (1 gap each)

These workflows have only one missing element and are lower priority:

File	Missing Element
daily-agent-of-the-day-blog-writer.md	no <details> usage
daily-ambient-context-optimizer.md	no report structure guidance
daily-architecture-diagram.md	no <details> usage
daily-astrostylelite-markdown-spellcheck.md	no <details> usage
daily-aw-cross-repo-compile-check.md	no report structure guidance
daily-awf-spec-compiler-surfacing.md	no report structure guidance
daily-cli-tools-tester.md	no <details> usage
daily-community-attribution.md	no report structure guidance
daily-doc-healer.md	no report structure guidance
daily-doc-updater.md	no report structure guidance
daily-experiment-report.md	no report structure guidance
daily-formal-spec-verifier.md	no report structure guidance
daily-function-namer.md	no report structure guidance
daily-geo-optimizer.md	no report structure guidance
daily-hippo-learn.md	no report structure guidance
daily-mcp-concurrency-analysis.md	no report structure guidance
daily-model-inventory.md	no report structure guidance
daily-multi-device-docs-tester.md	no report structure guidance
daily-news.md	no report structure guidance
daily-reliability-review.md	no report structure guidance
daily-safeoutputs-git-simulator.md	no report structure guidance
daily-security-observability.md	no report structure guidance
daily-sentrux-report.md	no report structure guidance
daily-skill-optimizer.md	no report structure guidance
daily-spdd-spec-planner.md	no report structure guidance
daily-syntax-error-quality.md	no report structure guidance
daily-team-evolution-insights.md	no report structure guidance
daily-workflow-updater.md	no report structure guidance
weekly-editors-health-check.md	no report structure guidance
weekly-safe-outputs-spec-review.md	no report structure guidance

Next Steps

• Add ## Output Format section to each of the 14 non-compliant workflow prompts
• Recompile each updated workflow (make recompile or gh aw compile)
• Address the 30 lower-priority "needs improvement" workflows as a follow-up batch
• Re-run workflow-normalizer after changes to confirm compliance

References: §27281166218

Generated by 🔧 Workflow Normalizer · 109.9 AIC · ⌖ 22.7 AIC · ⊞ 33.6K · ◷

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