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

Daily review of agentic workflow prompts against the project's report-formatting style guidelines (h3+ headers, progressive disclosure via <details>, clear report structure). Reviewed 47 reporting workflows (daily-*/weekly-* with create-issue, create-discussion, or add-comment safe-outputs). Found 10 non-compliant workflows lacking explicit header-level and/or progressive-disclosure guidance in their prompt instructions.

Non-Compliant Workflows

Required Changes

For each workflow above, add an explicit Output Format / Report Formatting section to the prompt instructions (near the end, before technical requirements) stating:

1. Headers: "Use ### (h3) or lower for all report headers; never use # or ## inside the report body."
2. Progressive disclosure: "Wrap long lists, tables, and detailed findings in <details><summary><b>...</b></summary>...</details> blocks to reduce scrolling."
3. Report structure: overview → key metrics/issues → collapsible detail → next actions.

Example: Progressive Disclosure Pattern

### Summary

Found 3 issues requiring attention.

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

- [ ] Issue 1: description
- [ ] Issue 2: description
- [ ] Issue 3: description

</details>

Good Reference Examples

• .github/workflows/daily-doc-healer.md (### Output Format section, explicit h3+ and <details> rule)
• .github/workflows/daily-model-resolution.md (### Report Formatting section)
• .github/workflows/daily-cache-strategy-analyzer.md (### Report Formatting section)
• daily-repo-chronicle and audit-workflows for overall report tone/structure (chronicle already has partial <details> guidance but is missing the explicit h3+ header rule)

Design Principles (Airbnb-inspired)

• Trust through clarity: keep key metrics visible; push verbose data into <details>.
• User-focused: structure reports so users can decide quickly what needs action.
• Consistent experience: apply the same formatting pattern across all reports.

Acceptance Criteria

• Each listed workflow has an explicit ### Output Format or ### Report Formatting section
• Each section specifies h3+ headers and <details>/<summary> progressive disclosure
• Workflows are recompiled with make recompile after edits

Generated by 🔧 Workflow Normalizer · auto · 44.8 AIC · ⌖ 2.25 AIC · ⊞ 10.5K · ◷

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