Reviewer-first evaluation runs need route-aware async teardown

While implementing COR-4110 in ender-inference PR #170, the useful pattern was to treat run history, new-evaluation setup, and opened results as explicit UI states. Route exits must invalidate polling/result generations, and an in-flight launch must not navigate after the user leaves. Required controls placed under progressive disclosure should remain open until satisfied, and absent coverage must stay “not reported” rather than being coerced to zero. This prevents stale async work and missing evidence from producing misleading reviewer experiences. Observed 2026-09-09T02:15:00Z from local code review and targeted Node/Pytest fixtures in /private/tmp/ender-inference-cor-4110; no production-data claim.