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

[github-actions]

Overview

Daily review of workflow activity (last 24 hours) identified 1 non-compliant reporting workflow out of 17 analyzed. Most workflows already comply via shared/reporting.md import or explicit inline formatting guidance. One workflow is non-compliant and requires an upstream fix due to its source-managed status.

Compliance Summary

Metric	Count
Active workflows (last 24h)	20
With markdown files in this repo	17
✅ Compliant	14
⏭️ Skipped (not reporting/test harness)	2
❌ Non-compliant	1

Non-Compliant Workflows

File	Name	Issue	Fix Path
.github/workflows/daily-team-status.md	Team Status	Missing h3+ header guidance, no <details> usage, no shared/reporting.md import	Upstream (githubnext/agentics)

View: detailed findings for daily-team-status.md

Current state — The workflow prompt has a ## Style section that says "Be positive, encouraging, and helpful 🌟" but provides no instruction about:

• Which header levels to use in the output (h1/h2 are implicitly allowed)
• When to collapse long content with <details> blocks
• What report structure to follow

Current prompt (style section):

## Style

- Be positive, encouraging, and helpful 🌟
- Use emojis moderately for engagement
- Keep it concise - adjust length based on actual activity

Required additions:

## Output Format

- Use `###` (or lower) for all headers — never `#` or `##`
- Wrap long activity lists in `<details>` blocks for progressive disclosure
- Structure: brief summary → highlights table → `<details>` with full activity log → next steps
- Import `shared/reporting.md` (or add explicit header/details guidance)

Why this matters: The workflow creates daily GitHub issues visible to the whole team. Issues with #/## headers break document hierarchy when embedded in GitHub's issue renderer and make the page feel harder to scan than a well-structured ###-based report.

Note: This file has source: githubnext/agentics/workflows/team-status.md@main making it read-only in this repository. The fix must be applied upstream.

Recommended Fix

For daily-team-status.md (upstream fix in githubnext/agentics):

Option A — add shared/reporting.md import to frontmatter:

imports:
  - shared/reporting.md

Option B — add explicit output format guidance to the prompt body:

## Output Format

Use `###` or lower for all headers. For long activity sections, apply progressive disclosure:

<details>
<summary><b>📋 Full Activity Log</b></summary>

[detailed list here]

</details>

Good Examples to Reference

The following active workflows demonstrate compliant reporting patterns:

• daily-function-namer.md — explicit inline guidance: "Use h3 (###) or lower for all headers in the issue body. Never use h1 (#) or h2 (##)."
• agent-performance-analyzer.md — imports shared/reporting.md
• constraint-solving-potd.md — uses <details> blocks and ###/#### headers natively
• github-mcp-structural-analysis.md — imports shared/daily-audit-base.md (which bundles shared/reporting.md)

Next Steps

• Submit upstream PR to githubnext/agentics to add shared/reporting.md import (or equivalent guidance) to workflows/team-status.md
• After upstream merge, run gh aw update to pull the updated daily-team-status.md
• Monitor next daily run to confirm the agent produces ###-headed issues with collapsible sections

References: §27554465877

Generated by 🔧 Workflow Normalizer · 633.1 AIC · ⌖ 13.1 AIC · ⊞ 33.3K · ◷

• expires on Jun 16, 2026, 7:00 AM UTC-08:00