Replay: Build GitHub data adapters for goal reconstruction

[smota]

Background & Problem Statement

Epic: #127

Replay MVP must work from GitHub alone. It needs adapters that collect relevant durable data without requiring local checkout, raw transcripts, or runner state.

Proposed Solution

Add GitHub adapter functions that load issues, comments, PRs, commits, checks/statuses, linked child issues, and follow-up references for a selected goal/epic/issue/PR.

Requirements

• Load epic/child issue hierarchy from body links, labels, and references.
• Load issue comments and workflow markers.
• Load PR body, commits, mergedAt, merge commit, checks/status summaries where available.
• Resolve follow-up links from comments/body.
• Rate-limit and pagination behavior documented.
• No raw transcript/session reads.

Acceptance criteria

• Adapter returns complete replay source bundle for issue or PR input.
• Pagination handles >100 comments/commits.
• Missing permissions fail with actionable error.
• Unit tests mock GitHub API calls.

Test plan

• Mocked GitHub client tests.
• Fixture tests with parent epic + child issues + merged PR.
• Permission/error path tests.

Workflow classification

Standard tooling/product feature.

[github-actions]

Integrated into development by PR #133: #133

Merge commit: 823d2e784f61e11645d2902e35401134fe0b1bdc
Release/promotion to main is tracked separately.

[smota]

AgentFlow whole-model alignment

This issue was aligned with the current AgentFlow SDLC product model for screenshot/demo consistency.

• Product area: product:cockpit, product:harness
• Release assignment: v1.0.0 / release:v1.0.0
• Workflow state: Implemented on development; included in v1 release model.
• Compatibility rule: GitHub/CLI durable workflow remains authoritative; generated harness surfaces stay adapters only.
• Cockpit is treated as optional first-class Goal Command Center: package/release-gated, runtime opt-in, no unique state.

No implementation change is implied by this metadata-only alignment comment.