Add gh aw logs summary command for CI markdown reports

[Copilot]

Adds a summary subcommand to gh aw logs that generates GitHub-flavored markdown suitable for piping to $GITHUB_STEP_SUMMARY in GitHub Actions workflows.

Changes

• New command: gh aw logs summary [workflow] [flags]

  • Outputs markdown to stdout (not stderr) for easy piping
  • Reuses existing logs download infrastructure via summary.json intermediate file
  • Supports all standard filtering: --firewall, --engine, --start-date, --count, etc.

• Markdown output includes:

  • Metrics summary table (runs, duration, tokens, cost, errors)
  • Firewall analysis with top 10 domains (allowed/denied counts)
  • Errors and warnings grouped by type (auto-truncates long messages)
  • Missing tools and MCP server failures

Usage

- name: Firewall summary
  if: always()
  run: gh aw logs summary --firewall >> $GITHUB_STEP_SUMMARY

gh aw logs summary weekly-research --start-date -1w -c 5

Implementation

• pkg/cli/logs_summary_command.go - Command implementation and markdown generation
• pkg/cli/logs_summary_command_test.go - Test suite covering data loading, markdown generation, edge cases
• pkg/cli/logs_command.go - Registered subcommand via AddCommand()

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Use awf logs summary for CI firewall reports</issue_title>
<issue_description>Use awf logs summary to generate markdown reports in GitHub Actions.

- name: Firewall summary
  if: always()
  run: awf logs summary >> $GITHUB_STEP_SUMMARY

Ref: githubnext/gh-aw-firewall#118</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Use awf logs summary for CI firewall reports #9041

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[pelikhan]

Agent got lost