Tool request: download workflow run artifact contents

從提議的入口點 download_workflow_run_artifact(owner, repo, run_id, artifact_name) 開始，並檢視列出的用於探索和下載 artifact 的 REST 端點。完成的標準是：一次 MCP 工具呼叫即可取得所選 workflow artifact 的內容，包括用於執行後分析的 token-usage.jsonl，而不要求呼叫方串接 REST 呼叫或自行解壓縮 artifact。

Problem

For cost tracking and post-run analysis of agentic workflows, the missing piece is read access to workflow run artifacts. Specifically, downloading the agent-artifacts artifact from a completed gh aw run to parse token-usage.jsonl for per-run token cost data.

The current workaround requires chaining several REST API calls:

1. GET /repos/{owner}/{repo}/actions/runs/{run_id}/artifacts to list artifacts
2. GET /repos/{owner}/{repo}/actions/artifacts/{artifact_id}/zip to download
3. Unzip and parse the relevant file

This is a lot of plumbing for what should be a natural thing for an AI agent to do: "look at what the last run produced."

Proposed tool

download_workflow_run_artifact(owner, repo, run_id, artifact_name) that returns the artifact contents (or a structured representation for known formats like JSONL).

Why this matters

The token-usage.jsonl format written by gh-aw's firewall proxy (since v0.25.8) contains per-model token counts for every agentic workflow run. A single MCP tool call to retrieve it would unlock a natural class of "analyze what the last agent run did" workflows. Right now that analysis requires dropping out of MCP and into raw REST.

More broadly, artifacts are a primary output mechanism for GitHub Actions. Being able to read them via MCP would make a wide range of post-run analysis workflows significantly simpler.