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

[github-actions]

Summary

Five report-generating workflows use bare #/## headers and skip <details> progressive disclosure, breaking consistency with the project's reporting skill guidelines (headers start at ###, long content collapses behind <details><summary><b>...</b></summary>).

Non-compliant workflows

Workflow	Issue
.github/workflows/daily-arxiv-researcher.md	Uses # / ## headers; no <details> usage
.github/workflows/daily-pr-review-cursor.md	Uses # / ## headers; no <details> usage
.github/workflows/daily-regression-audit-kiro.md	Uses # / ## headers; no <details> usage
.github/workflows/daily-schema-audit-cursor.md	Uses # / ## headers; no <details> usage
.github/workflows/daily-spec-coverage-kiro.md	Uses # / ## headers; no <details> usage

Required changes (per workflow)

1. Header levels: rewrite report-generation instructions so the top-level report heading is ### and nested sections are #### or lower — never #/##.
2. Progressive disclosure: add explicit guidance to wrap long/verbose sections (full findings lists, raw logs, per-item detail) in collapsible <details> blocks with bold <summary> labels.
3. Report structure: reference the shared reporting skill (or equivalent structure notes) so the workflow states its report format explicitly instead of leaving it implicit.

Example: progressive disclosure pattern

### Daily Regression Audit — 2026-08-09

**Runs analyzed**: 42 | **Regressions found**: 3

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

1. **workflow-a**: intermittent timeout in step 2
2. **workflow-b**: new lint failure
3. **workflow-c**: flaky network dependency

</details>

### Next Steps

- [ ] Triage regression-b
- [ ] File follow-up for workflow-c

Good references

• .github/workflows/daily-repo-chronicle.md — compliant header levels + <details> usage
• .github/workflows/audit-workflows.md — compliant header levels + <details> usage

Acceptance criteria

• Each listed workflow's prompt uses ###+ headers for its generated report
• Each listed workflow's prompt instructs use of <details>/<summary> for long content
• make recompile run after edits and .lock.yml files updated

Generated by 🔧 Workflow Normalizer · auto · 31.9 AIC · ⌖ 2.45 AIC · ⊞ 10.4K · ◷

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

[github-actions]

🍪 Issue Monster selected this for Copilot

I have 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 · gpt54 · 2.15 AIC · ⌖ 4.99 AIC · ⊞ 6.9K · ◷

[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 · gpt54 · 1.26 AIC · ⌖ 4.13 AIC · ⊞ 9K · ◷