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

[github-actions]

Overview

A daily style-normalization review (§27419763920) scanned 35 reporting workflows active in the last 24 hours against the project's markdown formatting guidelines. 3 workflows need updates to improve report readability and consistency.

Compliance Summary

Metric	Value
Workflows reviewed	35
Compliant	32 ✅
Non-compliant	3 ⚠️

Non-Compliant Workflows

Workflow File	Issues Found	Output Type
daily-team-status.md ⚠️ upstream-managed	No header-level guidance for output; no <details> guidance	GitHub Issue
daily-rendering-scripts-verifier.md	No header-level guidance for PR body; no <details> guidance	Pull Request
repository-quality-improver.md	Has h3 guidance ✅ but no <details> / progressive disclosure guidance	GitHub Discussion

Note on daily-team-status.md: This is an upstream-managed workflow (source: githubnext/agentics/workflows/daily-team-status.md@d3422bf9...). It must not be edited directly. The fix should be submitted upstream and pulled in via gh aw update.

Required Changes per Workflow

daily-team-status.md (upstream change required)

The prompt currently has no output formatting guidance. The generated daily status issue uses free-form headers that may start at h1/h2.

Add to the ## Style section (upstream):

- Use `###` (h3) or lower for all section headers in the issue body
- Wrap long activity lists in `<details><summary>View Full Activity</summary>` blocks

---

daily-rendering-scripts-verifier.md

The workflow creates PR bodies when rendering issues are found. No header or disclosure guidance exists.

Add a ## Output Format section before ## Guidelines:

## Output Format

When creating a pull request:
- Use `###` (h3) or lower for all headers in the PR body
- Wrap verbose test output or log excerpts in `<details>` blocks:

Parser test output

[paste output here]

``` - Keep critical fix summary visible; collapse raw logs ```

---

repository-quality-improver.md

The workflow already instructs h3+ headers ✅ but lacks guidance on progressive disclosure for the generated discussion.

Add to ## Phase 2: Generate Improvement Report after the h3 bullet:

- Wrap detailed findings lists and raw metric outputs in `<details><summary><b>View Details</b></summary>` blocks
- Keep the Executive Summary and task list visible; collapse secondary data

Progressive Disclosure Pattern Reference

Preferred structure for reports generated by these workflows:

### Summary
- Metric A: value
- Metric B: value
- Status: ✅ / ⚠️ / ❌

### Key Findings
[Always visible — decision-relevant items only]

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

[Verbose data, logs, per-item breakdowns]

</details>

### Next Steps
- [ ] Action item 1
- [ ] Action item 2

Good reference examples already using this pattern:

• audit-workflows.md — full <details> usage
• daily-experiment-report.md — progressive disclosure throughout
• copilot-session-insights.md — collapsible sections for per-run data

Acceptance Criteria

• daily-rendering-scripts-verifier.md — ## Output Format section added with h3 and <details> guidance
• repository-quality-improver.md — <details> guidance added to Phase 2 instructions
• daily-team-status.md — upstream PR submitted (or upstream ref bumped after merge)

References: §27419763920

Generated by 🔧 Workflow Normalizer · 225.3 AIC · ⌖ 13.8 AIC · ⊞ 33.7K · ◷

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