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

[github-actions]

Context

Automated review of reporting workflows identified 11 workflows that need improvements to their report/issue output formatting guidelines. These workflows create issues or discussions but either use h1/h2 headers in output templates or lack explicit style guidance.

Reference: Well-formatted workflows like daily-repo-chronicle and daily-spdd-spec-planner already follow these guidelines — use them as examples.

---

Non-Compliant Workflows

Workflow File	Issues Found
copilot-agent-analysis.md	No explicit h3+ header guidance; no <details> guidance in output section
copilot-pr-merged-report.md	Output template uses h2 (##); no h3 guidance; no <details> guidance
copilot-pr-nlp-analysis.md	Output template uses h2 (##); no explicit <details> guidance
daily-agentrx-trace-optimizer.md	Output template uses h2 (##); no h3 guidance; no <details> guidance
daily-ambient-context-optimizer.md	No explicit <details> guidance in issue output section
daily-aw-cross-repo-compile-check.md	Output template uses h2 (##); no explicit <details> guidance
daily-formal-spec-verifier.md	Output template uses h1 (#) and h2 (##); no h3 guidance; no <details> guidance
daily-mcp-concurrency-analysis.md	Output template uses h2 (##)
daily-sentrux-report.md	No explicit <details> guidance in output section
prompt-clustering-analysis.md	No explicit h3+ header guidance; no <details> guidance
static-analysis-report.md	Output template uses h2 (##); no h3 guidance; no <details> guidance

---

Required Changes

For each workflow listed, make the following updates in the output/issue format section of the prompt:

1. Header Level Guidance (workflows missing this)

Add an explicit instruction such as:

Use `###` or lower for all headers in your report. Never use `#` (h1) or `##` (h2) — these are reserved for the issue title rendered by GitHub.

2. Fix Output Templates Using h1/h2

Replace header lines in issue/discussion body templates:

• # Title → ### Title
• ## Section → ### Section or #### Section

Affected files: copilot-pr-merged-report.md, copilot-pr-nlp-analysis.md, daily-agentrx-trace-optimizer.md, daily-aw-cross-repo-compile-check.md, daily-formal-spec-verifier.md, daily-mcp-concurrency-analysis.md, static-analysis-report.md

3. Progressive Disclosure Guidance (workflows missing this)

Add a <details> guidance note in the output section:

Wrap long sections (>5 items, detailed lists, raw data) in `<details><summary><b>Section Name</b></summary>` blocks to keep the report scannable.

Example: Progressive Disclosure Pattern

Before (verbose, forces scrolling):

### All Findings

- Finding 1: ...
- Finding 2: ...
[20+ more items]

After (progressive disclosure):

### Summary

- **Total**: 23 findings across 5 workflows
- **Critical**: 2 | **High**: 6 | **Medium**: 15

<details>
<summary><b>All Findings (23)</b></summary>

- Finding 1: ...
[remaining items]

</details>

---

Good Examples to Reference

• daily-spdd-spec-planner.md — explicit ### or lower guidance + <details> wrapping instructions
• daily-repo-chronicle.md — well-structured progressive disclosure pattern
• daily-ambient-context-optimizer.md — good h3 discipline in output template (just needs <details> guidance)

---

Next Steps

• Update each listed workflow file with the required changes above
• Verify templates in daily-formal-spec-verifier.md (uses both h1 and h2 in output)
• Run make recompile after any .github/workflows/*.md changes
• Confirm next workflow run produces properly formatted reports

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔧 Workflow Normalizer · 65 AIC · ⌖ 6.55 AIC · ⊞ 5.5K · ◷

• expires on Jul 9, 2026, 5:25 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 2.71 AIC · ⌖ 5.55 AIC · ⊞ 4.6K · ◷