The commits page shows each commit's check beside it, green, red or not run, and a commit's own page says why, as MCP `commits` does #7507

Intent: reading history in the browser tells which commits were green, without opening runs one by one. MCP commits and the terminal's one-commit view read checkOfCommit (src/actions/runs.ts). The web commits page (src/web/pages/commits.ts) does not.

Done:

• [ ] Each row drawn by commitRows carries a small verdict: a green or red badge with the word, or nothing when no check ran, linked to that check's run. Rows are read in one batch per page (at most the page's commits), never one query per row. Add a batched read beside checkOfCommit if needed.
• [ ] A single commit's page (renderCommit) says the verdict in a sentence, and on red names the first failing test, as MCP commits does.
• [ ] Only checks the viewer may see are shown; a sealed run is left out.
• [ ] Run bun scripts/design-lint.ts, using existing badge classes.
• [ ] A test (e.g. test/web-commits-check.test.ts) records a green and a red check on two commits, renders the page and finds both verdicts and the link. A commit with no check shows none.

Files: src/web/pages/commits.ts, src/actions/runs.ts, a new test.