# Oversized GitLab MR response runtime evidence

PR: [#24215](https://github.com/pingdotgg/t3code/pull/24215)
After revision: fea14ef4b44bb814dac74941c3b8dd1f11fbebad (merge preserving original contribution; changed files identical to 239f282268 per lead). Before revision: main 27e0c684c5 (lead-provided).
Environment: /home/ubuntu/wt/issue-24201; existing web http://localhost:6899, server localhost:14939; isolated worktree .t3. No server started or stopped by evidence sub-agent.
Fixture: private GitLab project julius54/t3-issue-24201-repro, id 88036520; checkout /tmp/issue-24201/repo. Both open MRs have description `release notes\n` followed by 600000 x characters. Same fixture used before/after.
Input: Pull Requests; state Open; involvement All; Filters > Project, All projects selected.

## Independent observations
Both supplied PNGs opened and visually inspected by evidence sub-agent.
Before: Project menu shows `repo · Unavailable`; fixture MR rows absent from visible list.
After: Project menu shows available `repo`; visible rows are `#2 Draft: oversized description fixture 2` and `#1 Draft: oversized description fixture 1`, repository julius54/t3-issue-24201-repro.
The before/after captures are supplemental runtime evidence. Unrelated live PR timestamps/order were not controlled. No pixel comparison claims.
Render matrix: EMPTY (server-only diff), 0/0; no new screenshots or diff images required.

Read-only fixture command independently executed:
`glab api 'projects/88036520/merge_requests?state=opened&order_by=updated_at&sort=desc&per_page=26&page=1'`
Actual response: 1203535 bytes, two opened MRs:
- iid 2, id 554744760, Draft: oversized description fixture 2
- iid 1, id 554744748, Draft: oversized description fixture 1
This raw glab check corroborates the fixture; it alone does not establish adapter success.

## Lead-provided validation
Actual integrated UI after change successfully lists both MRs from the same oversized response, with the project available, as also visible in inspected capture.
Red revision 840a4207a0: `vp test run src/server/GitLabPullRequestCli.test.ts -t 'larger than the VCS default'` from the GitLab package fails with GitLabMergeRequestReadError, unreadable list JSON (provided by lead; not rerun here).
After: 43/43 focused tests and 110 package tests pass (provided by lead; not rerun here).

## Lead semantic runtime observation
The lead read the running patched app through preview_evaluate on its existing browser tab at 2026-10-24 approximately 09:54 UTC. The attached browser-observation.json records the live URL, Open/All inputs, both fixture MR rows, and the Project submenu with repo available (no Unavailable suffix). This is the real app fetching through the running server adapter; no mock or component harness was used. Runtime HEAD is fea14ef4b44bb814dac74941c3b8dd1f11fbebad. Browser viewport 1280x800 CSS px, DPR 2, Linux headless Chromium, no device emulation, default font scaling, light theme.

```json
{
  "url": "http://localhost:6899/pull-requests?involvement=all&state=open",
  "inputs": {
    "state": "open",
    "involvement": "all"
  },
  "fixtureRows": [
    "#2\nDraft: oversized description fixture 2\njulius54\njulius54/t3-issue-24201-repro\n4m ago",
    "#1\nDraft: oversized description fixture 1\njulius54\njulius54/t3-issue-24201-repro\n4m ago"
  ],
  "menus": [
    "State\nOpen\nInvolvement\nAll\nAuthor\nAnyone\nLabels\nAny\nDraft\nAll\nReview\nAll\nChecks\nAll\nHost\nAll\nProject\nAll projects",
    "Project\nAll projects\nRO\nrepo\nSR\nserver"
  ],
  "viewport": {
    "width": 1280,
    "height": 800,
    "dpr": 2
  }
}

```

## Red output
At 840a4207a0, implementation unchanged from main 27e0c684c5:
```
× reads a page of merge requests larger than the VCS default output limit
GitLabMergeRequestReadError: GitLab CLI failed in listMergeRequests: GitLab CLI returned an unreadable listMergeRequests response.
SchemaError: Expected a valid JSON string
Tests 1 failed | 42 skipped (43)
```
Lead reran focused file after integration at fea14ef4b4: 43 passed in 937 ms.

FRICTION: the child could not read the lead-owned browser tab; lead supplied the live semantic observation directly.