[workflow-style] Normalize report formatting for daily-firewall-report

[github-actions]

Workflow to Update

Workflow File: .github/workflows/daily-firewall-report.md
Issue: This workflow generates firewall analysis reports but doesn't include markdown style guidelines

Required Changes

Update the workflow prompt to include these formatting guidelines:

1. Header Levels

Add instruction: "Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy."

2. Progressive Disclosure

Add instruction: "Wrap detailed request logs and domain lists in <details><summary><b>Section Name</b></summary> tags to improve readability and reduce scrolling."

Example:

<details>
<summary><b>Full Request Log Details</b></summary>

[Long detailed content here...]

</details>

3. Report Structure

Suggest a structure like:

• Brief summary of firewall activity (always visible)
• Key metrics (requests, blocks, trends) (always visible)
• Detailed request patterns (in <details> tags)
• Top blocked/allowed domains (in <details> tags)
• Security recommendations (always visible)

Design Principles (Airbnb-Inspired)

The updated workflow should create reports that:

1. Build trust through clarity: Most important info immediately visible
2. Exceed expectations: Add helpful context, trends, and security insights
3. Create delight: Use progressive disclosure to reduce overwhelm
4. Maintain consistency: Follow the same patterns as other reporting workflows

Example Reference

See workflows like daily-repo-chronicle, daily-issues-report, or audit-workflows for good examples of structured reporting with progressive disclosure.

Agent Task

Update the workflow file .github/workflows/daily-firewall-report.md to include the formatting guidelines above in the prompt instructions. Test the updated workflow to ensure it produces well-formatted reports.
Related to #11271

AI generated by Workflow Normalizer

• expires on Jan 31, 2026, 12:23 PM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster