feat proposal(mcp): Include repository and organization fields in `logs` tool response

[jaroslawgajewski]

Problem

The agentic-workflows MCP logs tool returns per-episode metadata (tokens,
cost, duration, MCP failures, blocked requests), but does not include the
repository or organization that triggered the run.

This makes it impossible for any downstream consumer — observability exporters,
audit workflows, cost dashboards — to group, filter, or attribute runs by
repository.

Current behavior

The logs tool response contains:

• run_id, workflow_names, started_at, total_tokens, total_estimated_cost
• total_duration, mcp_failure_count, blocked_request_count
• action_minutes, trigger

Missing: repository (full name), organization

Expected behavior

Each episode in the logs response should include:

Field	Type	Example
repository	string	"org_name/repo_name"
organization	string	"org_name"

These are already available in the GitHub Actions context (GITHUB_REPOSITORY,
github.repository_owner) and in aw_info.json — they just need to be surfaced
in the MCP response.

Use cases unlocked

• Cost attribution: "Which repo spends the most on agentic workflows?"
• Cross-repo audit: org-pr-audit scans multiple repos — attributing cost
  per target repo is impossible without this field.
• Observability export: External platforms (Langfuse, Datadog, custom dashboards)
  need repo context for meaningful filtering.
• Org-level dashboards: Enterprise customers managing multiple repos need
  org-level aggregation.

Suggested implementation

Surface GITHUB_REPOSITORY and github.repository_owner from the workflow run
context into the episode metadata schema returned by the logs tool.