[Phase 4B] Post-merge: PR history view with proof snapshots

[frankbria]

Goal

Add a PR history view to the Review page listing recently merged PRs alongside their PROOF9 proof reports at time of merge.

Background

First half of the post-merge glitch capture loop. After PRs merge, users need to see what was shipped and what proof was attached — so they can identify which PR introduced a production glitch.

Scope

PR History section on the Review page (shown below the PR Status panel, or as a tab):

• Lists the last 10 merged PRs for the workspace: PR title, merge date, author, link to GitHub
• Each row shows a proof snapshot badge: how many gates passed / total at time of merge (e.g., "7/9 gates passed")
• Clicking a row expands to show the gate-by-gate breakdown at time of merge
• Backend: GET /api/v2/pr/history?workspace=...&limit=10 — queries merged PRs from GitHub API and joins with proof run records stored in the DB by PR number
• Empty state: "No merged PRs yet" with link to Review page workflow

Acceptance criteria

• PR history list renders with title, date, proof snapshot
• Expanding a row shows gate breakdown
• Backend endpoint returns correct merged PR + proof data
• npm test and uv run pytest pass

[coderabbitai]

🔗 Related PRs

#491 - feat(web-ui): surface PROOF9 gate link in execution completion banner (#469) [merged]
#496 - feat(web-ui): link failed tasks to PROOF9 gate failure for root cause (#474) [merged]
#525 - feat(web-ui): PRD version history panel with diff and restore [merged]
#526 - feat(web-ui): sort and filter controls for Proof requirements table [merged]
#528 - feat(web-ui): filter, search, and sort for proof evidence history table [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[traycerai]

Warning

Ticket Assist will be discontinued on May 1, 2026. After that date, the feature will no longer be available. We suggest installing the Traycer IDE Extension for continued AI-powered, spec-driven development. Thank you for choosing Traycer!

Plan

Observations

The active web UI (web-ui/) is a Next.js 16 + React 19 app using swr, axios, @radix-ui, and @hugeicons/react. The Review page (web-ui/src/app/review/page.tsx) already has a CommitPanel, ReviewHeader, and PRCreatedModal. The backend uses FastAPI v2 routers under /api/v2/pr (file:codeframe/ui/routers/pr_v2.py) with GitHubIntegration for GitHub API calls. Proof data lives in the proof_requirements and proof_evidence SQLite tables per workspace (file:codeframe/core/proof/ledger.py). There is no existing proof_run_snapshots table or PR-number-to-proof-run join — this must be introduced. The pull_requests table in file:codeframe/persistence/schema_manager.py tracks merged PRs by pr_number and merged_at.

Approach

The key design challenge is the "proof snapshot at time of merge" join. Since proof runs are workspace-scoped (not PR-scoped), the cleanest approach is to introduce a lightweight pr_proof_snapshots table in the workspace's SQLite DB (alongside proof_requirements) that records gate pass/fail counts at the moment a PR is created via the v2 endpoint. The new GET /api/v2/pr/history endpoint then fetches merged PRs from GitHub and joins with these snapshots by PR number. This keeps everything in the existing workspace-DB pattern used by ledger.py and avoids touching the global state.db.

---

Implementation Steps

1. Add pr_proof_snapshots table to the proof ledger

In file:codeframe/core/proof/ledger.py, extend init_proof_tables to also create a pr_proof_snapshots table:

Column	Type	Description
pr_number	INTEGER PRIMARY KEY	GitHub PR number
workspace_id	TEXT	Workspace identifier
gates_passed	INTEGER	Count of satisfied obligations at snapshot time
gates_total	INTEGER	Total obligations at snapshot time
gate_breakdown	TEXT	JSON array of {gate, status} objects
snapshotted_at	TEXT	ISO timestamp

Add a save_pr_proof_snapshot(workspace, pr_number, gates_passed, gates_total, gate_breakdown) function and a get_pr_proof_snapshot(workspace, pr_number) function following the same raw-sqlite3 pattern as save_evidence / list_evidence.

---

2. Snapshot proof state when a PR is created

In file:codeframe/ui/routers/pr_v2.py, in the create_pull_request endpoint (the POST /api/v2/pr handler), after the GitHub API call succeeds and the PRResponse is ready:

• Call list_requirements(workspace) from codeframe.core.proof.ledger
• Compute gates_passed = count of obligations with status == "satisfied" across all requirements
• Compute gates_total = total obligation count across all requirements
• Build gate_breakdown = list of {gate, status} for each obligation
• Call save_pr_proof_snapshot(workspace, pr.number, gates_passed, gates_total, gate_breakdown)

This captures the proof state at PR creation time, which is the closest proxy to "at time of merge" without requiring a webhook.

---

3. Add PRHistoryItem and PRHistoryResponse Pydantic models

In file:codeframe/ui/routers/pr_v2.py, add new response models:

• ProofSnapshotOut — gates_passed: int, gates_total: int, gate_breakdown: list[GateBreakdownItem]
• GateBreakdownItem — gate: str, status: str
• PRHistoryItem — number: int, title: str, merged_at: str, author: str | None, url: str, proof_snapshot: ProofSnapshotOut | None
• PRHistoryResponse — pull_requests: list[PRHistoryItem], total: int

---

4. Add GET /api/v2/pr/history endpoint

In file:codeframe/ui/routers/pr_v2.py, add a new route before the /{pr_number} route to avoid path conflicts:

GET /api/v2/pr/history?workspace=...&limit=10

• Decorated with @rate_limit_standard()
• Accepts limit: int = Query(10, ge=1, le=50) and workspace: Workspace = Depends(get_v2_workspace)
• Calls await client.list_pull_requests(state="closed") on GitHubIntegration
• Filters results where pr.merged_at is not None, sorts by merged_at descending, takes [:limit]
• For each merged PR, calls get_pr_proof_snapshot(workspace, pr.number) and attaches the snapshot (or None if not found)
• Also reads author from the raw GitHub API response — extend _parse_pr_response or make a separate raw-data pass (the GitHub API returns user.login in the PR object)
• Returns PRHistoryResponse

Note: GitHubIntegration.list_pull_requests currently only passes state as a query param. To get merged PRs, pass state="closed" and filter client-side on merged_at is not None. Alternatively, extend list_pull_requests to accept a per_page param for efficiency.

---

5. Extend GitHubIntegration to expose author

In file:codeframe/git/github_integration.py:

• Add author: Optional[str] field to PRDetails dataclass
• In _parse_pr_response, populate it from data.get("user", {}).get("login")

---

6. Add TypeScript types for PR history

In file:web-ui/src/types/index.ts, add:

• GateBreakdownItem — { gate: string; status: string }
• ProofSnapshot — { gates_passed: number; gates_total: number; gate_breakdown: GateBreakdownItem[] }
• PRHistoryItem — { number: number; title: string; merged_at: string; author: string | null; url: string; proof_snapshot: ProofSnapshot | null }
• PRHistoryResponse — { pull_requests: PRHistoryItem[]; total: number }

---

7. Add prApi.getHistory to the API client

In file:web-ui/src/lib/api.ts, extend the prApi object with:

getHistory: async (workspacePath: string, limit?: number): Promise<PRHistoryResponse>

Calls GET /api/v2/pr/history with workspace_path and optional limit query params.

---

8. Create PRHistoryPanel component

Create web-ui/src/components/review/PRHistoryPanel/index.tsx (following the directory-per-component pattern used by FileTreePanel, DiffViewer, etc.).

Structure:

PRHistoryPanel/
  index.tsx          ← main export
  PRHistoryRow.tsx   ← single expandable row
  ProofBadge.tsx     ← "7/9 gates passed" badge
  GateBreakdown.tsx  ← expanded gate-by-gate table

PRHistoryPanel (index.tsx):

• Accepts workspacePath: string
• Uses useSWR with key ['pr/history', workspacePath] calling prApi.getHistory(workspacePath)
• Renders a loading skeleton (3 rows, matching LoadingSkeleton style in file:legacy/web-ui/src/components/pr/PRList.tsx)
• Empty state: "No merged PRs yet" message with a link back to the Review page workflow
• Error state: retry button
• Maps pull_requests to PRHistoryRow components

PRHistoryRow:

• Displays: PR title, merge date (formatted with date-fns), author, GitHub link (using Link01Icon from @hugeicons/react)
• Shows ProofBadge inline
• On click, toggles expanded state to show GateBreakdown
• Uses ArrowDown01Icon / ArrowUp01Icon for expand/collapse affordance

ProofBadge:

• Receives gates_passed and gates_total
• Renders "{gates_passed}/{gates_total} gates passed" with color coding:
  • All passed → text-green-600 bg-green-50
  • Partial → text-yellow-600 bg-yellow-50
  • None / no snapshot → text-muted-foreground bg-muted with "No proof data"

GateBreakdown:

• Receives gate_breakdown: GateBreakdownItem[]
• Renders a compact table with gate name and status icon (checkmark for satisfied, X for failed/pending)

---

9. Integrate PRHistoryPanel into the Review page

In file:web-ui/src/app/review/page.tsx:

• Import PRHistoryPanel
• Add it below the CommitPanel in the right sidebar, or as a collapsible section below the main 3-column layout — the simplest approach is to add it as a new full-width section below the <div className="flex min-h-0 flex-1 gap-4 p-4"> block, visible when workspacePath is set

---

10. Register the new route in server.py

The pr_v2.router is already mounted at /api/v2/pr in file:codeframe/ui/server.py. No change needed — the new /history sub-route is automatically included.

---

Data flow summary

sequenceDiagram
    participant UI as PRHistoryPanel
    participant API as GET /api/v2/pr/history
    participant GH as GitHub API
    participant DB as Workspace SQLite (pr_proof_snapshots)

    UI->>API: GET /api/v2/pr/history?workspace_path=...&limit=10
    API->>GH: list_pull_requests(state="closed")
    GH-->>API: List of closed PRs
    API->>API: Filter merged_at != null, sort desc, take limit
    loop For each merged PR
        API->>DB: get_pr_proof_snapshot(workspace, pr.number)
        DB-->>API: ProofSnapshot or None
    end
    API-->>UI: PRHistoryResponse {pull_requests: [...]}
    UI->>UI: Render rows with ProofBadge
    UI->>UI: On row click → expand GateBreakdown

Loading

Import In IDE

🤖 Prompt for AI Agents

## Observations

The active web UI (`web-ui/`) is a Next.js 16 + React 19 app using `swr`, `axios`, `@radix-ui`, and `@hugeicons/react`. The Review page (`web-ui/src/app/review/page.tsx`) already has a `CommitPanel`, `ReviewHeader`, and `PRCreatedModal`. The backend uses FastAPI v2 routers under `/api/v2/pr` (`file:codeframe/ui/routers/pr_v2.py`) with `GitHubIntegration` for GitHub API calls. Proof data lives in the `proof_requirements` and `proof_evidence` SQLite tables per workspace (`file:codeframe/core/proof/ledger.py`). There is **no** existing `proof_run_snapshots` table or PR-number-to-proof-run join — this must be introduced. The `pull_requests` table in `file:codeframe/persistence/schema_manager.py` tracks merged PRs by `pr_number` and `merged_at`.

## Approach

The key design challenge is the "proof snapshot at time of merge" join. Since proof runs are workspace-scoped (not PR-scoped), the cleanest approach is to introduce a lightweight `pr_proof_snapshots` table in the workspace's SQLite DB (alongside `proof_requirements`) that records gate pass/fail counts at the moment a PR is created via the v2 endpoint. The new `GET /api/v2/pr/history` endpoint then fetches merged PRs from GitHub and joins with these snapshots by PR number. This keeps everything in the existing workspace-DB pattern used by `ledger.py` and avoids touching the global `state.db`.

---

## Implementation Steps

### 1. Add `pr_proof_snapshots` table to the proof ledger

In `file:codeframe/core/proof/ledger.py`, extend `init_proof_tables` to also create a `pr_proof_snapshots` table:

| Column | Type | Description |
|---|---|---|
| `pr_number` | INTEGER PRIMARY KEY | GitHub PR number |
| `workspace_id` | TEXT | Workspace identifier |
| `gates_passed` | INTEGER | Count of satisfied obligations at snapshot time |
| `gates_total` | INTEGER | Total obligations at snapshot time |
| `gate_breakdown` | TEXT | JSON array of `{gate, status}` objects |
| `snapshotted_at` | TEXT | ISO timestamp |

Add a `save_pr_proof_snapshot(workspace, pr_number, gates_passed, gates_total, gate_breakdown)` function and a `get_pr_proof_snapshot(workspace, pr_number)` function following the same raw-sqlite3 pattern as `save_evidence` / `list_evidence`.

---

### 2. Snapshot proof state when a PR is created

In `file:codeframe/ui/routers/pr_v2.py`, in the `create_pull_request` endpoint (the `POST /api/v2/pr` handler), after the GitHub API call succeeds and the `PRResponse` is ready:

- Call `list_requirements(workspace)` from `codeframe.core.proof.ledger`
- Compute `gates_passed` = count of obligations with `status == "satisfied"` across all requirements
- Compute `gates_total` = total obligation count across all requirements
- Build `gate_breakdown` = list of `{gate, status}` for each obligation
- Call `save_pr_proof_snapshot(workspace, pr.number, gates_passed, gates_total, gate_breakdown)`

This captures the proof state at PR creation time, which is the closest proxy to "at time of merge" without requiring a webhook.

---

### 3. Add `PRHistoryItem` and `PRHistoryResponse` Pydantic models

In `file:codeframe/ui/routers/pr_v2.py`, add new response models:

- `ProofSnapshotOut` — `gates_passed: int`, `gates_total: int`, `gate_breakdown: list[GateBreakdownItem]`
- `GateBreakdownItem` — `gate: str`, `status: str`
- `PRHistoryItem` — `number: int`, `title: str`, `merged_at: str`, `author: str | None`, `url: str`, `proof_snapshot: ProofSnapshotOut | None`
- `PRHistoryResponse` — `pull_requests: list[PRHistoryItem]`, `total: int`

---

### 4. Add `GET /api/v2/pr/history` endpoint

In `file:codeframe/ui/routers/pr_v2.py`, add a new route **before** the `/{pr_number}` route to avoid path conflicts:

```
GET /api/v2/pr/history?workspace=...&limit=10
```

- Decorated with `@rate_limit_standard()`
- Accepts `limit: int = Query(10, ge=1, le=50)` and `workspace: Workspace = Depends(get_v2_workspace)`
- Calls `await client.list_pull_requests(state="closed")` on `GitHubIntegration`
- Filters results where `pr.merged_at is not None`, sorts by `merged_at` descending, takes `[:limit]`
- For each merged PR, calls `get_pr_proof_snapshot(workspace, pr.number)` and attaches the snapshot (or `None` if not found)
- Also reads `author` from the raw GitHub API response — extend `_parse_pr_response` or make a separate raw-data pass (the GitHub API returns `user.login` in the PR object)
- Returns `PRHistoryResponse`

> **Note:** `GitHubIntegration.list_pull_requests` currently only passes `state` as a query param. To get merged PRs, pass `state="closed"` and filter client-side on `merged_at is not None`. Alternatively, extend `list_pull_requests` to accept a `per_page` param for efficiency.

---

### 5. Extend `GitHubIntegration` to expose `author`

In `file:codeframe/git/github_integration.py`:

- Add `author: Optional[str]` field to `PRDetails` dataclass
- In `_parse_pr_response`, populate it from `data.get("user", {}).get("login")`

---

### 6. Add TypeScript types for PR history

In `file:web-ui/src/types/index.ts`, add:

- `GateBreakdownItem` — `{ gate: string; status: string }`
- `ProofSnapshot` — `{ gates_passed: number; gates_total: number; gate_breakdown: GateBreakdownItem[] }`
- `PRHistoryItem` — `{ number: number; title: string; merged_at: string; author: string | null; url: string; proof_snapshot: ProofSnapshot | null }`
- `PRHistoryResponse` — `{ pull_requests: PRHistoryItem[]; total: number }`

---

### 7. Add `prApi.getHistory` to the API client

In `file:web-ui/src/lib/api.ts`, extend the `prApi` object with:

```
getHistory: async (workspacePath: string, limit?: number): Promise<PRHistoryResponse>
```

Calls `GET /api/v2/pr/history` with `workspace_path` and optional `limit` query params.

---

### 8. Create `PRHistoryPanel` component

Create `web-ui/src/components/review/PRHistoryPanel/index.tsx` (following the directory-per-component pattern used by `FileTreePanel`, `DiffViewer`, etc.).

**Structure:**

```
PRHistoryPanel/
  index.tsx          ← main export
  PRHistoryRow.tsx   ← single expandable row
  ProofBadge.tsx     ← "7/9 gates passed" badge
  GateBreakdown.tsx  ← expanded gate-by-gate table
```

**`PRHistoryPanel` (index.tsx):**
- Accepts `workspacePath: string`
- Uses `useSWR` with key `['pr/history', workspacePath]` calling `prApi.getHistory(workspacePath)`
- Renders a loading skeleton (3 rows, matching `LoadingSkeleton` style in `file:legacy/web-ui/src/components/pr/PRList.tsx`)
- Empty state: "No merged PRs yet" message with a link back to the Review page workflow
- Error state: retry button
- Maps `pull_requests` to `PRHistoryRow` components

**`PRHistoryRow`:**
- Displays: PR title, merge date (formatted with `date-fns`), author, GitHub link (using `Link01Icon` from `@hugeicons/react`)
- Shows `ProofBadge` inline
- On click, toggles expanded state to show `GateBreakdown`
- Uses `ArrowDown01Icon` / `ArrowUp01Icon` for expand/collapse affordance

**`ProofBadge`:**
- Receives `gates_passed` and `gates_total`
- Renders `"{gates_passed}/{gates_total} gates passed"` with color coding:
  - All passed → `text-green-600 bg-green-50`
  - Partial → `text-yellow-600 bg-yellow-50`
  - None / no snapshot → `text-muted-foreground bg-muted` with "No proof data"

**`GateBreakdown`:**
- Receives `gate_breakdown: GateBreakdownItem[]`
- Renders a compact table with gate name and status icon (checkmark for satisfied, X for failed/pending)

---

### 9. Integrate `PRHistoryPanel` into the Review page

In `file:web-ui/src/app/review/page.tsx`:

- Import `PRHistoryPanel`
- Add it below the `CommitPanel` in the right sidebar, or as a collapsible section below the main 3-column layout — the simplest approach is to add it as a new full-width section below the `<div className="flex min-h-0 flex-1 gap-4 p-4">` block, visible when `workspacePath` is set

---

### 10. Register the new route in `server.py`

The `pr_v2.router` is already mounted at `/api/v2/pr` in `file:codeframe/ui/server.py`. No change needed — the new `/history` sub-route is automatically included.

---

### Data flow summary

```mermaid
sequenceDiagram
    participant UI as PRHistoryPanel
    participant API as GET /api/v2/pr/history
    participant GH as GitHub API
    participant DB as Workspace SQLite (pr_proof_snapshots)

    UI->>API: GET /api/v2/pr/history?workspace_path=...&limit=10
    API->>GH: list_pull_requests(state="closed")
    GH-->>API: List of closed PRs
    API->>API: Filter merged_at != null, sort desc, take limit
    loop For each merged PR
        API->>DB: get_pr_proof_snapshot(workspace, pr.number)
        DB-->>API: ProofSnapshot or None
    end
    API-->>UI: PRHistoryResponse {pull_requests: [...]}
    UI->>UI: Render rows with ProofBadge
    UI->>UI: On row click → expand GateBreakdown
```

---

Execution Information

Branch: main
Commit: ea0de0a

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.