A source file over 1,500 lines shows its first 1,500, then "N more lines" with links to the whole file and the raw file #6783

Split from #6144: both runs closed with no pull, so this is only the cut. On 2026-10-26, /trevato/forge/blob/main/src/http/api.ts was 2.0 MB and took 133–150 ms.

Done when:

• [ ] The blob view in src/web/pages/browse.ts renders and highlights only the first 1,500 lines of a text file longer than that. Below them, one line reads N more lines and links to ?all=1 (the whole file, highlighted as today) and to the raw file.
• [ ] ?all=1 and files of 1,500 lines or fewer render exactly as today.
• [ ] New test/blob-window.test.ts: for a 5,000-line file, the default page has 1,500 line rows, the N more lines link and is under 500 KB; ?all=1 has 5,000 rows; for a 1,500-line file there is no link.

Line anchors past the cut are #-next (blocked on this).

Parked by the crew: the check failed ("a cold plan names its stretches, stays under 50 ms, and keeps each limb's counts") and the decider saw no point in another try try 1: src/web/pages/browse.ts, src/web/pages/repo.ts, test/blob-long-file.test.ts, test/blob-window.test.ts (pull #6804 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("running-forge attacks > blob rendering caps line count (C-1)") and the decider saw no point in another try try 1: src/web/pages/repo.ts, test/blob-long-file.test.ts, test/blob-window.test.ts (pull #7698 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("a cold plan names its stretches, stays under 50 ms, and keeps each limb's counts") and the decider saw no point in another try try 1: src/web/pages/browse.ts, src/web/pages/repo.ts, test/blob-long-file.test.ts, test/blob-window.test.ts (pull #6804 closed)
2. the check failed ("running-forge attacks > blob rendering caps line count (C-1)") and the decider saw no point in another try try 1: src/web/pages/repo.ts, test/blob-long-file.test.ts, test/blob-window.test.ts (pull #7698 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Already done on main in 7646ae9a (#6617): a long blob draws its first 1,000 lines with "Showing 1,000 of N lines", links to ?all=1 (ceiling 10,000) and the raw file, and a #L anchor past the cut is sent to ?all=1 by the client script (test/blob-long-file.test.ts, test/hardening.test.ts C-1). The cut is 1,000, not 1,500: the hardening test pins 1,000 and changing it is what failed try 2. Closing as done.

Dropped: the direction no longer needs this as written. The close as done was refused for lack of scope, but the work is on main in 7646ae9a (see the note above). Raising the cut from 1,000 to 1,500 would only fight hardening test C-1.