Active run details no longer cached

Active and running builds were being cached, which meant developers watching an in-progress run would see stale trace data instead of real-time updates. The fix introduces a check for terminal statuses — COMPLETED, CANCELED, FAILED, CRASHED, SYSTEM_FAILURE, EXPIRED, and TIMED_OUT — and only caches runs that have reached one of these final states. Active runs now fetch fresh data on every request, giving developers accurate, up-to-the-second information while they wait for their builds to finish. This lives in the MCP tools layer of the CLI, specifically in the runs.ts file.