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

[github-actions]

Overview

54 reporting workflows were reviewed for compliance with the project's markdown style guidelines. 2 workflows are non-compliant and need formatting improvements.

Compliance Status

• ✅ Compliant: 52 workflows follow style guidelines
• ⚠️ Needs Improvement: 2 workflows need updates

---

Non-Compliant Workflows

Workflow File	Missing: h3+ Header Guidance	Missing: <details> Progressive Disclosure
daily-squid-image-scan.md	✅	✅
daily-vulnhunter-scan.md	✅	✅

Required Changes for Each Workflow

daily-squid-image-scan.md

Current prompt instructs the agent to create issues with findings but provides no formatting guidance. The issue bodies may use arbitrary header levels.

Changes needed:

1. Add header level guidance: instruct the agent to use ### or lower in generated issue bodies
2. Add progressive disclosure: instruct the agent to wrap long vulnerability lists in <details><summary>View all findings</summary>...</details>

Example addition to prompt:

Format each issue using `###` headers or lower (never `#` or `##`).
For images with more than 3 vulnerabilities, wrap the full list in a
`<details><summary><b>All vulnerabilities</b></summary>` block.

daily-vulnhunter-scan.md

Current prompt instructs the agent to create a single security issue but has no report formatting rules.

Changes needed:

1. Add header level guidance: enforce ### or lower in issue body
2. Add progressive disclosure: wrap detailed evidence/code snippets in <details> blocks

Example addition to prompt:

Structure the issue body using `###` headers or lower.
Wrap detailed code snippets or reproduction steps in
`<details><summary><b>Evidence</b></summary>` blocks.

---

Example: Progressive Disclosure Pattern

Reference implementation from daily-repo-chronicle.md and audit-workflows.md:

### Summary

Brief overview visible at a glance.

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

#### Detail Section

Long content here...

</details>

Next Steps

• Update daily-squid-image-scan.md prompt with h3+ and <details> instructions
• Update daily-vulnhunter-scan.md prompt with h3+ and <details> instructions
• Monitor next run to verify generated issue bodies comply

Review Date: 2026-07-25
Workflows Reviewed: 54 (daily- and weekly- prefix + key reporting workflows)

Generated by 🔧 Workflow Normalizer · sonnet46 · 32.8 AIC · ⌖ 9.05 AIC · ⊞ 7.3K · ◷

• expires on Jul 26, 2026, 5:08 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 · 3.26 AIC · ⌖ 6.62 AIC · ⊞ 6.4K · ◷