The lane is visible: queue depth, the running check and its age, median duration and the time to clear, on the home and in /api/v1/health; the 30-minute card names the cause #1538

The lane is now visible on the home and in /api/v1/health, and a lapsed run no longer shows as working. tsc --noEmit is clean and bun test passes for vitals, board and check-list. I did not run the whole suite; the forge runs the full check on this push.

What changed

• Lane data: src/kernel/vitals.ts adds lane: {queued, running: {pull, since}, medianMinutes, clearsInMinutes}. It comes from the run table, with the median taken over the last 20 finished checks. laneLine() renders Lane: 43 checks queued · running #1171 for 6 min · median 20 min · clears in ~14 h, or nothing when the queue is empty.
• Health: the same lane object is in /api/v1/health.
• 30-minute card: it now carries the lane line and says it is one lane with checks running one at a time.
• Home strip (site admin only): it shows the lane line. It also shows a row per live agent run, linking to the run. When none is live it says Crew idle: nothing ready or Crew idle: autonomy off.
• Stale runs (owner's 04:30Z acceptance): a running run whose heartbeat is stale for more than 90 s now shows lost, re-queuing. It is not counted as working, in the strip or on the board.
• Merge: I merged main in. The earlier failures were the gate-list guard and a test conflict; I settled the one conflicting assertion in test/vitals.test.ts (vitals now makes 5 queries, up from 3 on main).

Left out

• The card does not name the fast-tier cause or link a fixing issue. That needs a source for "pulls branched after 17:12", which doesn't exist yet.
• The crew row shows agent run, repo, pull and start time, but not a one-line "what it is doing".
• There is no test/web.test.ts case; the strip is covered in test/board.test.ts.
• ceiling reached is not offered as a reason for an idle crew.

Try it Sign in as a site admin and open the home; seed queued check runs to see the line. Run bun test test/vitals.test.ts test/board.test.ts.

🤖 Generated with Claude Code

Closes #1277

I've pushed the three fixes. The board, vitals and terminal dashboard tests pass and tsc --noEmit is clean. I didn't run the whole suite; the forge's check does that.

• Terminal dashboard: an admin's strip now shows the lane line (Lane: 3 checks queued · running #12 for 4 min · median 20 min · clears in ~1 h). I added forgeLane in src/actions/health.ts, and src/tui/screens/dashboard.ts appends the line when checks are queued. Non-admins get nothing. A test in test/tui-screens.test.ts checks that the admin sees the lane, that it is absent with no queue, and that a non-admin never sees it. The README now says the lane shows on the home strip, the terminal dashboard and GET /api/v1/health.
• Scope: I removed the "lost, re-queuing" run state, its CSS, crewRows and the "Crew idle" / "agent on …" rows, along with their test. I did not add a crew line to the terminal, because that would mean building the thing you asked me to drop. If you want the crew rows, they should come back as their own issue under their own pillar.
• Cause text: laneLine no longer includes the Lane: label; the board and terminal add it themselves. The 30-minute card is built from parts joined with ; , so it can't produce . ;. A test pins the full sentence and checks that it has no Lane: prefix. I also put the long board.ts import back to its original shape.