`enter` on a run in the terminal opens its log, the last 200 lines, refreshing while it runs, as MCP `run_log` does #7293

For: the owner who wants to see why a crew run failed without leaving the terminal. Today enter on a run only prints a web address (openRunLog in src/tui/screens/runlist.ts).

runLog (src/actions/runs.ts) is reached from the run page and MCP run_log. No terminal screen reads it.

Done:

• [ ] A new src/tui/screens/runlog.ts: the run's state line, then its last 200 log lines, scrolled to the end; j/k and page keys scroll; it rereads every 2 s while the run is queued or running and stops when it ends.
• [ ] openRunLog pushes this screen; o on it still prints the web address.
• [ ] A hidden log or a repository the viewer cannot read says "not found", as the REST route does; nothing of it is drawn.
• [ ] A new test/tui-runlog.test.ts: a finished run shows its last lines; a hidden log reads not found; a running run's new lines appear after a reread.

Files: src/tui/screens/runlog.ts, src/tui/screens/runlist.ts, one test. Risk: low; read only.