Repository navigation
[workflow-style] Normalize report formatting for non-compliant workflows #70262
Description
Overview
The last 24-hour review covered 18 active report-oriented workflow prompts (daily/weekly reports, audits, status/metrics reports, and the normalizer path). Four need formatting improvements to make generated reports easier to scan and consistent with the repository reporting conventions. The cached run set contained 335 usable records; 68 malformed or incomplete records were skipped.
Compliance Status
- ✅ Compliant: 14 workflows
⚠️ Needs Improvement: 4 workflows- Issues Created: 1 consolidated issue
Non-Compliant Workflows
| Workflow file | Findings |
|---|---|
.github/workflows/daily-work-queues-report.md |
Report prompt starts with #; it does not require <details> for long queue/item details; report structure should explicitly separate visible overview, queue table, limitations, and actions. |
.github/workflows/daily-windows-defender-scan.md |
Report template uses # and ##; it lacks progressive-disclosure guidance for raw logs/evidence and does not define a consistently visible summary versus detailed evidence layout. |
.github/workflows/daily-workflow-security-model.md |
Finding-report instructions use lower-level structure inconsistently and do not require <details> for lengthy evidence; make the report sections and next actions explicit. |
.github/workflows/metrics-collector.md |
Metrics output has detailed schema/instructions but no progressive-disclosure guidance for human-facing summaries; define a concise visible overview and collapsible metric detail sections. |
Required Changes
For each listed workflow:
- Use
###or lower for generated report headings; reserve#and##for GitHub-rendered issue/PR titles. - Put long evidence, raw logs, item lists, and metric detail inside
<details><summary><b>...</b></summary>blocks. - Define a clear report structure: visible overview/key metrics and issues first, then collapsible findings/evidence, followed by actionable next steps and limitations.
- Preserve the existing safety, evidence, and safe-output behavior.
Progressive Disclosure Example
### Summary
- **Status**: Needs attention
- **Findings**: 2
- **Next action**: Review the linked evidence
<details>
<summary><b>Detailed findings</b></summary>
#### Finding 1
Evidence, links, and raw diagnostic detail go here.
</details>Good References
Use .github/workflows/daily-repo-chronicle.md and .github/workflows/audit-workflows.md as reference points for concise report guidance, visible summaries, and collapsible detail patterns. Keep run references in the repository format, for example §39255976049.
Next Steps
- Update the four workflow prompts with h3+ headings, progressive disclosure, and explicit report structure.
- Recompile affected workflows and review the next report-producing runs.
- Recheck the normalizer’s next 24-hour window for compliance.
Generated by 🔧 Workflow Normalizer · codex · gpt56 · 2.34 AIC · ⌖ 0.608 AIC · ⊞ 14.8K · ◷
- expires on Oct 20, 2026, 5:09 AM UTC-08:00
Activity
github-actions commentedon Oct 20, 2026
This issue was automatically closed because it expired on 2026-10-20T13:09:16.317Z.