An lcov coverage file in a repository opens as a table: each source file's line and branch coverage, worst first, linked to the file #11077

A file named lcov.info or *.lcov now opens as a coverage table instead of raw text. I haven't run it against a running app. tsc, the gate, the design lint and the render, kinds, fuzz and sarif-page tests pass; the full suite and forge.json's check were not run here.

• Table: line, function and branch percentages for the whole file sit at the top, as a one-line summary. Below is one row per SF: record, worst line coverage first. Each row shows lines, functions and branches (only when the file has any) as hit/found, with a bar for line coverage. The bars are native <meter> elements, so there is no script and no inline style. If a record has no LF/LH, lines are counted from its DA: lines.
• Links: a path links to the file at the ref only when it is a plain relative path that exists there. This reuses sarif's path check and RenderInput.exists. Absolute paths, .. paths and missing files stay plain text. The browse and repo pages now fetch the existing-paths list for lcov files too, as they do for SARIF.
• Caps and fallback: at most 5,000 records are drawn and the rest are counted. Parsing is a single linear pass. A malformed file shows the source with the reason and line number. Malformed means:

- a counter or DA line outside a record; - a counter that is not a number; - only one of an LF/LH pair; - more hit than found; - a record missing end_of_record; - no records at all.

• Where: src/web/render/lcov.ts is new, and kinds.ts, renderers.ts and the two page files are extended. The kind is chosen by name (lcov.info or .lcov) and capped at 5 MB.
• Tests: test/render-lcov.test.ts has the two-file report (hand-counted totals), the absolute path, malformed records, the 5,000 cap and escaping. I also added lcov entries to the kinds and fuzz tests.

I did not draw per-line DA or branch detail, or FN/BRDA records, and did not add a TUI view; the terminal still shows the source. The pre-push hook asked for a Try: line in a commit message, so the commit has one.

Closes #11073

A file named lcov.info or *.lcov now opens as a coverage table instead of raw text. I haven't run it against a running app. tsc, the gate, the design lint and the render, kinds, fuzz and sarif-page tests pass; the full suite and forge.json's check were not run here.

• Table: line, function and branch percentages for the whole file sit at the top, as a one-line summary. Below is one row per SF: record, worst line coverage first. Each row shows lines, functions and branches (only when the file has any) as hit/found, with a bar for line coverage. The bars are native <meter> elements, so there is no script and no inline style. If a record has no LF/LH, lines are counted from its DA: lines.
• Links: a path links to the file at the ref only when it is a plain relative path that exists there. This reuses sarif's path check and RenderInput.exists. Absolute paths, .. paths and missing files stay plain text. The browse and repo pages now fetch the existing-paths list for lcov files too, as they do for SARIF.
• Caps and fallback: at most 5,000 records are drawn and the rest are counted. Parsing is a single linear pass. A malformed file shows the source with the reason and line number. Malformed means:

- a counter or DA line outside a record; - a counter that is not a number; - only one of an LF/LH pair; - more hit than found; - a record missing end_of_record; - no records at all.

• Where: src/web/render/lcov.ts is new, and kinds.ts, renderers.ts and the two page files are extended. The kind is chosen by name (lcov.info or .lcov) and capped at 5 MB.
• Tests: test/render-lcov.test.ts has the two-file report (hand-counted totals), the absolute path, malformed records, the 5,000 cap and escaping. I also added lcov entries to the kinds and fuzz tests.

I did not draw per-line DA or branch detail, or FN/BRDA records, and did not add a TUI view; the terminal still shows the source. The pre-push hook asked for a Try: line in a commit message, so the commit has one.

I made no code change for this failure. I think it is a timing flake and have pushed an empty commit to re-run the check.

budgets > /map and / answer under their p95 and statement budgets is in test/snappy.test.ts. It failed in shard 41 at 1507 ms, while 77 shards were running at once. This pull touches only lcov rendering, the file-kind registry and the two blob pages, none of which / or /map use. I ran the file alone three times here and all 6 tests passed each time.

If the check fails the same way on the re-run, that would point at a real slowdown and I'll look at it properly.

All four items from the review are done and pushed. The gate, tsc, the design lint and test/render-lcov.test.ts plus test/tui-workspace.test.ts (42 tests) pass here. I did not run the full suite; the forge's check does that on the push.

• Feature doc: docs/features/file-lcov.md is added next to file-sarif.md.
• Terminal door: lcov.info now opens in the workspace as a table of File, Lines, Functions and Branches, worst first. The status line reads "N files", and s flips to the source. It uses the same parseLcov as the page. A broken file shows the source with the reason, as with SARIF. A new test in test/tui-workspace.test.ts covers the ordering, the counts and the file total.
• Design: I dropped the lcov-view class, so the page uses only the existing table and meter components.
• Duplicate check: needsPaths(kind) in src/web/render/kinds.ts is now the single check, and repo.ts and browse.ts both call it.

Not done: the terminal's rows are text only, with no meter bars or file links.

The gate's "pipeline first" rule failed because the pull adds docs/features/file-lcov.md and changes nothing in the pipeline. I made no pipeline change. Instead I pushed an empty commit with a Direction: line saying the lcov view is what issue #11073 asks for and that review required its feature doc, so it displaces no pipeline item.

bun scripts/gate.ts now passes locally with no output. I did not re-run tsc or the tests, since the empty commit changes no files. The forge's check will run them on this push.

An lcov tracefile (lcov.info, *.lcov) in a repository now opens as a coverage table on the page and in the terminal, instead of raw text. Source stays one tap away. The gate, tsc, the design lint, test/render-lcov.test.ts and test/tui-workspace.test.ts (42 tests) pass locally.

Page. src/web/render/lcov.ts reads the file in one pass. The top line gives total coverage of lines, functions and branches. Below it is one row per source file, with a <meter> bar and hit/found counts plus a percentage for each measure, worst line coverage first. A file links to itself at the same ref when its path is a plain relative path that exists there. At most 5,000 files are drawn and the page says how many were left out. A malformed file falls back to the source with the reason. Every string is escaped, and the page uses only the existing table and meter components, with no new CSS class.

Terminal. lcovTable in src/tui/screens/workspace.ts shows File, Lines, Functions and Branches, with "N files" in the status line. s flips to the source, and a broken file shows its source with the reason.

Shared pieces. Both views use the same parseLcov and the same worstFirst sort from lcov.ts, so their order cannot drift apart. needsPaths(kind) in kinds.ts is the one place that decides when repo.ts and browse.ts load the ref's file list.

What to look at:

• docs/features/file-lcov.md is the how-to.
• test/tui-workspace.test.ts opens a good lcov.info and checks the worst-first order and the file count. It then opens a broken sub/lcov.info and checks that the reason is shown.
• One commit has a Direction: line: this is a feature and the "pipeline first" gate rule asks for that line. Juniper flagged it for a person to weigh.

Not done here (Juniper's suggested next steps):

• No page-level test checks that the browse and blob pages hand the renderer the file list; needsPaths is covered only by unit tests.
• The terminal shows text only: no meter bars or file links yet.

🤖 Generated with Claude Code

An lcov coverage file (lcov.info or *.lcov) now opens as a table with lines, functions and branches per source file, worst coverage first. Each file name links to that file in the repository. A file that isn't valid lcov opens as plain source with a note saying why it wasn't drawn as coverage. The terminal workspace shows the same table using the web's parser.

This push merges main, which had added JUnit reports in the same places. Both features are kept:

• src/web/render/kinds.ts: "lcov" and "junit" are both in FileKind, both have a 5 MB limit, and both are checked in fileKind. They don't overlap: lcov goes by file name, JUnit by .xml plus its root element.
• src/web/render/renderers.ts: both renderers are registered.
• src/tui/screens/workspace.ts: lcovTable and junitTable sit side by side, and so do their branches when a file opens. The status line shows main's "N failing case(s)" for JUnit and passes isLcovPath to tableStatus for everything else.

- Main now builds each table's grid inside its own branch, so the lcov branch builds its own. Without that line, the lcov file opened to an empty pane — the lcov test in test/tui-workspace.test.ts caught it.

• test/tui-workspace.test.ts: the lcov test and both JUnit tests are all kept.

tsc --noEmit passes and design-lint reports nothing to fix. scripts/gate.ts ran but printed nothing. scripts/fast.ts named 1860 test files, too many to run here, so I ran the six that cover the merged files: render-lcov, render-junit, render-kinds, fuzz-renderers, tui-workspace and tui-workspace-kinds. All 102 tests pass.

To try it, open an lcov.info in the preview: worst-covered files come first. A JUnit TEST-*.xml opens as before, as its totals and failing cases.

🤖 Generated with Claude Code