A check's run page shows install, typecheck and tests as step rows from the first paint #2564

A check's run page now shows install, typecheck and tests as three rows, each with a state, from the first paint, with the log tail below. Durations are not there yet, and the step states are inferred from the log. test/studio-runs.test.ts passes, including the new tests, and tsc --noEmit is clean. I did not run the full check.

• Step states: checkSteps(run, lines) in src/checks/summary.ts is a pure function that returns the three rows. It reads the run's state and its log lines, and adds no new record. The log has no step boundaries, so it infers progress from two signs: the echoed $ command lines, and the test-shards: banner or ── shard headers that mean tests have begun. Typecheck counts as done once tests begin, because it runs first in the check command. The step the run reached is running while it is live, and failed or stopped if it ended there. Later steps stay waiting, and a passed run shows all three as passed.
• Page: src/web/studio/run.ts renders an <ol id="check-steps"> only for kind === "check" runs. It always has three equal-height rows, so nothing shifts as states change. Small CSS in src/web/style/content.ts styles it. No other page changed.
• Tests: a running check shows install:ok, typecheck:ok, tests:running. A finished red one shows tests:failed. A fresh queued one still has three waiting rows.

What I left out:

• Durations: the log carries no per-step timestamps, so a duration would be a guess. I left it out rather than invent one. Showing it needs the runner (src/checks/service.ts) to write step start and end markers, which would be a separate change.
• Job-placed checks: these echo every command up front, so install only reads as done once output follows the echoes.
• Typecheck failures: a failure before the tests start is shown on the typecheck row. That is inferred, and it has no test of its own.

Try it by opening any check run at /<owner>/<repo>/runs/<id>.

🤖 Generated with Claude Code

Closes #2420

A check's run page now shows install, typecheck and tests as three rows, each with a state, from the first paint, with the log tail below. Durations are not there yet, and the step states are inferred from the log. test/studio-runs.test.ts passes, including the new tests, and tsc --noEmit is clean. I did not run the full check.

• Step states: checkSteps(run, lines) in src/checks/summary.ts is a pure function that returns the three rows. It reads the run's state and its log lines, and adds no new record. The log has no step boundaries, so it infers progress from two signs: the echoed $ command lines, and the test-shards: banner or ── shard headers that mean tests have begun. Typecheck counts as done once tests begin, because it runs first in the check command. The step the run reached is running while it is live, and failed or stopped if it ended there. Later steps stay waiting, and a passed run shows all three as passed.
• Page: src/web/studio/run.ts renders an <ol id="check-steps"> only for kind === "check" runs. It always has three equal-height rows, so nothing shifts as states change. Small CSS in src/web/style/content.ts styles it. No other page changed.
• Tests: a running check shows install:ok, typecheck:ok, tests:running. A finished red one shows tests:failed. A fresh queued one still has three waiting rows.

What I left out:

• Durations: the log carries no per-step timestamps, so a duration would be a guess. I left it out rather than invent one. Showing it needs the runner (src/checks/service.ts) to write step start and end markers, which would be a separate change.
• Job-placed checks: these echo every command up front, so install only reads as done once output follows the echoes.
• Typecheck failures: a failure before the tests start is shown on the typecheck row. That is inferred, and it has no test of its own.

Try it by opening any check run at /<owner>/<repo>/runs/<id>.

🤖 Generated with Claude Code

The check run page now shows install, typecheck and tests as three rows from the first paint, and the rows update while the run is open. test/check-steps.test.ts and test/studio-runs.test.ts pass and tsc --noEmit is clean; I did not run the full check.

I addressed the review points as follows:

• Live update: the run page's script (studioRunJs, src/web/client.ts) refetches the page and swaps in #check-steps. It does this about 400 ms after a log line that can change a row (a $ command echo, the test-shards: banner or a ── shard header), and again when the run ends. The test covers only that the page ships this wiring. I did not exercise the browser behaviour.
• Truncated log: checkSteps takes truncated. If the log was cut and the tests aren't visible in what remains, and the run didn't pass, all three rows read unknown. A passed run still reads passed, and a visible shard header still shows the tests.
• Hidden log: the rows are not rendered when the viewer can't read the log, so progress is no longer visible to them. The test uses a public repo that isn't an app.
• Tests:

- test/check-steps.test.ts is new and covers typecheck failure, install failure, no install command, a cancelled run, a passed run, a job-placed check and a truncated log. - test/studio-runs.test.ts covers the live-update script and the hidden-log case.

• README: it now describes the rows.

I did not add rows to the tty. A check run isn't read as a run there. The terminal's pull screen shows a one-line check summary (checksText), which stays as it is. The issue said only the run page should change, so I noted that in the README instead.

Per-step durations are still not shown. The log has no timestamps, so any figure would be a guess. Showing them needs src/checks/service.ts to write step start and end markers, which I left for a separate change.

🤖 Generated with Claude Code

The terminal's pull screen now shows the same three step rows as the run page. I changed the phone layout, the screen-reader announcement and the install match too. I ran test/check-steps.test.ts, test/studio-runs.test.ts and test/check-progress.test.ts; they pass and tsc --noEmit is clean. I did not run the full check.

• Terminal: the pull screen's checks line now ends with install passed · typecheck passed · tests running. It comes from stepsLine (src/checks/progress.ts), which reads the log through the same checkSteps the page uses, so the two can't disagree. It adds nothing for a deploy or when mayReadRunLog says the viewer can't read the log. The terminal has no per-run screen (a run opens as the web page), so the checks line is the only place a check shows there. The line truncates on a narrow terminal. The tests are in test/check-steps.test.ts.
• Phone: under 480px the rows stack into one column.
• Screen readers: the list has role="status" and aria-live="polite".
• Install match: it is now anchored to bun|npm|pnpm|yarn [flags] install|ci, so bun scripts/install-hooks.ts no longer counts as the install. A test covers it.
• README: it now describes the terminal line.

I did not add a test that drives the live refetch in a browser. The sandbox has none, so that path is still only checked by the string match in test/studio-runs.test.ts. The step states are still inferred from the log.

I left per-step durations out again. The log has no timestamps, so any figure would be a guess.

🤖 Generated with Claude Code