# Issue 17484 evidence

Head: f750ae4cf45468145341ef3050c1a5c7b09960d4; base: 70e5e384da; branch: fix/issue-17484.
Environment: /home/ubuntu/wt/issue-17484; Linux 6.1.102 x86_64; machine marker freestyle; Vite+ test runner v5.0.5.

Proof matrix: 0/0 render/capture rows. Server-only exception: red regression plus runtime transcript; no render, capture, video, diff image, or fixture script required.
Only AgentSessionScanner.ts and AgentSessionScanner.test.ts changed: 53 insertions, 16 deletions. No render code, contracts, or client changes. Scanner now enforces 100,000 records per transcript rather than depleting a shared record allowance. Byte/transcript budgets remain; aggregate record work can increase within those budgets. Claude and Codex share this reader.

## Evidence

- [Proof audit / empty matrix](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/3c49e363e355c9c2/issue-17484-proof-matrix.md)
- [RED regression](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/08925593d1f51a3e/issue-17484-red.txt): supplied primary transcript, test-only commit a67624fdfee8f165a70a857adbd9dfdf87f0b41a; fourth outcome Skipped instead of session-3.
- [GREEN actual command output](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/81663ae507682bd9/issue-17484-green.txt): run from apps/server with ../../node_modules/.bin/vp test run src/project/AgentSessionScanner.test.ts -t 'per-file record limit|excessive records|exact record limit'. Exit 0; 1 file passed; 4 passed, 50 skipped. Selected: new aggregate-valid regression; existing streaming excessive-record rejection with older valid transcript; standalone parser exact-cap and overflow cases. Exact-cap streaming behavior was source-inspected (recordCount > MAX_IMPORT_RECORDS); no dedicated exact-cap streaming test was added or claimed.
- [Runtime BEFORE](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/be68c8b00484b94f/issue-17484-runtime-before.txt): supplied primary observation, first import 3 with 1 skipped; retry imports fourth.
- [Runtime AFTER](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/1160f1df71e587d9/issue-17484-runtime-after.txt): supplied primary observation at fixed head, fresh isolated DB, discovery 4, first import 4, no retry; all four persisted. Same fixture counts 20,000 + 20,000 + 20,000 + 58,000 = 118,000.
- [Independent read-only persistence query](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/2d1534def51a95df/issue-17484-persistence.txt): mode=ro on worktree DB, all four fixture titles present. This verifies current persistence; fresh-first-import timing is supported by the primary transcript.

Optional visual context, captured by primary (not required server proof):

Before:
![Before: first import reports three threads with one skipped](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/fa2bd6ef2f01147a/browser-screenshot-localhost-mvipl8iy-399931ed.png)

After:
![After: successful import reports four threads](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/bb2a0fc2a90407d7/browser-screenshot-localhost-mviqului-a5a49f7b.png)

## Limits and handling

Test sub-agent started no browser or server, made no repository edits/commits or forge writes, and ran no full suite or typecheck. Worktree clean before and after execution. No auth files, environment files, or startup URLs read or uploaded. Uploaded logs and after screenshot reviewed for secrets; fixture-only content.
Windows desktop shell unverified and unnecessary for this server logic. Mobile/Android not exercised. Primary alone performed real-app before/after work; this sub-agent inspected supplied transcripts and the existing DB, and executed targeted green tests.

FRICTION none | Targeted tests and evidence upload succeeded | Keep explicit worktree, local vp path, and server-proof exception in the handoff.
END — evidence capture complete